[Q] Which Moto G stock firmware to use? - Moto G Q&A, Help & Troubleshooting

I'm looking to restore my Moto G to stock, but I don't know which version to choose.
Can anyone help me for which one I need because the one that I did flash, is the last one you see in the picture, and now my network (T-Mobile) isn't working anymore.
Also what is the difference between the AWSRetail.en.US and the Retail.en.US?

Model no. XT1032 is non-AWS. XT1034 is AWS. Only the later is compatible with T-Mobile’s 1700 (AWS) bands.

lost101 said:
Model no. XT1032 is non-AWS. XT1034 is AWS. Only the later is compatible with T-Mobile’s 1700 (AWS) bands.
Click to expand...
Click to collapse
Okay I really appreciate that info. Do you think you could by any chance help me fix the problem with my phone? It cant seem to connect to my carrier and the radio and gps is off. I really don't know how to fix this.. please help
And when I go into Settings>More...>Mobile Networks>Network Operators it tell says, "Error while searching for networks." And then when I try to press Choose Automatically, I get a message saying, " Your SIM card does not allow a connection to this network".
But that's not true because it has been working all this time.

Flash the AWSRetail.en.US stock firmware and everything should be fine again.

lost101 said:
Flash the AWSRetail.en.US stock firmware and everything should be fine again.
Click to expand...
Click to collapse
Are you sure? Because I actually have model no. XT1032
Also Im really sorry if I keep annoying you

Veyzo said:
Are you sure? Because I actually have model no. XT1032
Click to expand...
Click to collapse
How do you know this? All models state '1032' under About phone > Baseband version.
You have flashed the the retail XT1032 US stock firmware and radio is not working. That suggests a) have an XT1034 or b) you didn't flash correctly.

lost101 said:
How do you know this? All models state '1032' under About phone > Baseband version.
You have flashed the the retail XT1032 US stock firmware and radio is not working. That suggests a) have an XT1034 or b) you didn't flash correctly.
Click to expand...
Click to collapse
Yes I checked the Baseband version and it does say 1032. You might be right that it was flashed wrong, but Iv'e tried it about 3 times now it still isn't working.
Could you show me how to correctly flash it on a Mac? The guide I followed was the one here on xda-developers for the Moto G and I'm not sure what I could have done wrong, I really just need my network to work again.

Veyzo said:
Yes I checked the Baseband version and it does say 1032. You might be right that it was flashed wrong, but Iv'e tried it about 3 times now it still isn't working.
Could you show me how to correctly flash it on a Mac? The guide I followed was the one here on xda-developers for the Moto G and I'm not sure what I could have done wrong, I really just need my network to work again.
Click to expand...
Click to collapse
As I said, Baseband version is not an indicator of which model you have.
Fastboot flash: Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
As I said, Baseband version is not an indicator of which model you have.
Fastboot flash: Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Oh okay I understand. Well the way I know that it is XT1032 is because that is what it shows registered on my Google account. (check attached screenshot)

The answer is simple. Follow the guide, flash XT1032 firmware. If that doesn't work, flash XT1034 firmware.

lost101 said:
The answer is simple. Follow the guide, flash XT1032 firmware. If that doesn't work, flash XT1034 firmware.
Click to expand...
Click to collapse
Alright I will try doing that. Thanks for helping me

lost101 said:
The answer is simple. Follow the guide, flash XT1032 firmware. If that doesn't work, flash XT1034 firmware.
Click to expand...
Click to collapse
Okay so I flashed it, but the phone will not boot. It just stays stuck on the warning screen that tells you your bootloader is unlocked. And I was positive that I did flash it correctly because in the guide, it says that each command I enter in terminal should return with "OKAY" and they all did.
Here is my log in terminal with the commands I entered to flash the ROM (I bolded the commands and the OKAY'S) :
Last login: Thu Jul 17 17:17:15 on ttys000
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.027s]
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.359s]
finished. total time: 0.386s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.101s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.297s]
finished. total time: 1.398s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.091s]
writing 'logo'...
OKAY [ 0.137s]
finished. total time: 0.229s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.376s]
writing 'recovery'...
OKAY [ 1.004s]
finished. total time: 1.381s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (260693 KB)...
OKAY [ 8.202s]
writing 'system'...
OKAY [ 17.607s]
finished. total time: 25.809s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (261168 KB)...
OKAY [ 8.218s]
writing 'system'...
OKAY [ 15.416s]
finished. total time: 23.634s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (219321 KB)...
OKAY [ 6.915s]
writing 'system'...
OKAY [ 22.025s]
finished. total time: 28.940s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.527s]
writing 'modem'...
OKAY [ 2.279s]
finished. total time: 3.806s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.072s]
finished. total time: 0.072s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.071s]
finished. total time: 0.071s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (717 KB)...
OKAY [ 0.120s]
writing 'fsg'...
OKAY [ 5.355s]
finished. total time: 5.475s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase cache
erasing 'cache'...
OKAY [ 0.144s]
finished. total time: 0.144s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase userdata
erasing 'userdata'...
OKAY [ 2.202s]
finished. total time: 2.202s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot reboot
rebooting...
finished. total time: 0.001s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$
So what am I doing wrong here? Is there anything else I can do?

You did not flash boot.img
After recovery you should have
fastboot flash boot boot.img

All the fastboot commands in the correct order.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot​

alresave said:
You did not flash boot.img
After recovery you should have
fastboot flash boot boot.img
Click to expand...
Click to collapse
Oh wow can't believe I missed that.. I'll try it again and see what happens

lost101 said:
As I said, Baseband version is not an indicator of which model you have.
Fastboot flash: Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Dude you are the best! That one worked like you said and my network is working again! I really do appreciate the help! ::good::good::good::

alresave said:
You did not flash boot.img
After recovery you should have
fastboot flash boot boot.img
Click to expand...
Click to collapse
OMG Thanks so much man, you noticing that just saved my phone!

Related

[Q] Help! fastboot flash appears to do nothing!

I have somehow totally trashed my Android install. I have a UK retail Moto G XT1032.
While downloading the OTA lollipop update, the download appeared to stall. I decided to give up on the update, so I switched the phone off. When I turned it back on again, every single process crashed. "Unfortunately dialler/android.process.acore/Calendar/android.process.media/etc has stopped". I can keep tapping "OK" for ever to clear these notifications, but can't actually use the phone for anything at all.
So I decided to do a factory reset from fastboot. It made no difference.
I tried a factory reset from recovery. It made no difference.
Using fastboot, I attempted to install the stock ROM according to the guide at http://forum.xda-developers.com/showthread.php?t=2542219. Everything seemed to flash OK - I got OKAY on the PC and the commands appeared to be running on the phone OK, but when it restarted, the phone was exactly the same - my wallpaper photo was still there, and the app icons that I could glimpse behind the endless notifications were my apps.
I tried several more times, this time flashing the 4.4.4 ROM (RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF). Exactly the same results - nothing changes when I restart.
It's as if the mfastboot flash commands do nothing at all! I have run all the mfastboot commands described by the guide in the order given.
I've also tried booting to recovery and connecting to ADB, but the PC cannot see the device.
I've tried replacing the recovery with CWM and TWRP .img files, but the flash command, while seeming to work, doesn't change anything at all! The recovery that I have installed is the standard KXB21.14-L1.40.
I have tried "mfastboot.exe erase recovery", before attempting to update the recovery, but it makes no difference.
Does anybody have any idea what I am doing wrong? It seems that no "mfastboot flash xxx yyy" command works at all on my phone.
Did you installfastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.
Got the same problem. I've already posted this in a few threads and didn't get any answer, though
Sounds crazy but, when you type fastboot devices with your phone connected in fastboot mode, does the command return your phone's serial #?
Yes, everything via fastboot works (says complete, done etc.) except it doesn't affect the real system. If you sideload ADB you will see that the system, data and cache partition become read-only. I've managed to remount only data partition with write privileges, but that doesn't help.
Are you flashing each partition manually? You can see your device's serial # in fastboot?
audit13 said:
Did you install fastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.
Click to expand...
Click to collapse
Originally, I used the version of fastboot that came with the first stock ROM I tried (falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB).
Later on, I installed mfastboot and used that instead. The results were the same. Nothing seems to actually be flashed, but there are no errors on either the PC or the phone.
ADB does not work in fastboot (I don't believe it's supposed to!), but it also will not work with the version of recovery that I have, which is why I was attempting to install CWM and TWRP in its place.
audit13 said:
Are you flashing each partition manually? You can see your device's serial # in fastboot?
Click to expand...
Click to collapse
Yes. I'm currently trying the following sequence with the XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml ROM...
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
The mfastboot command returns OKAY for each of these, and a couple of yellow lines appear on the phone for each command, indicating that the right command is running, with no error messages.
I have never used mfastboot. Maybe try using fastboot to flash? I have used fastboot on my Moto G and Moto Atrix HD with great success.
Tried with fastboot, tried with mfastboot, got no errors but nothing changes. The real problem I suppose is corrupted partitions.
Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358
@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?
dog121 said:
Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358
Click to expand...
Click to collapse
I've just given it a go.
When flashing the ROMs, it basically runs the same mfastboot commands that I was running before, so the result was exactly the same.
However, the ADB Driver install button was worth trying. The driver supplied has enabled my PC to communicate with the phone using ADB when in recovery mode!
Unfortunately, after selecting "apply update from ADB" on the phone, and running "adb sideload <ROM zip file>", it sends it to the phone (taking a couple of minutes), and the phone says "Verifying update package", followed by "Installation aborted".
When you sideload, do you need some sort of special format ROM file?
audit13 said:
@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?
Click to expand...
Click to collapse
I was hoping to use the stock ROM, just to get the phone back to its original state.
If the mfastboot command does nothing, I doubt trying different ROMs will help. But I'll probably try it if I can't get anything else to work.
thanks a lot!
@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot​
lost101 said:
@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot​
Click to expand...
Click to collapse
Thanks for the idea. I happen to have a laptop running the latest Lubuntu.
I installed fastboot as you directed and re-flashed everything. Exactly the same. The commands all say OKAY, the yellow text on the phone says it's running the commands, but when I reboot - everything is exactly as it was before - including my wallpaper photo and app icons. And every single process on the phone is crashing.
I do not believe fastboot is actually working on this phone. The only commands that seem to work are the ones to unlock the bootloader and the one to reboot the phone.
@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
I.e first file is sparsechunk.0 not sparsechunk1
EDIT: Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
It's retail Brazil, but will work anywhere in the world.
I suggest you skip flashing the bootloader - motoboot.img
lost101 said:
@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
Click to expand...
Click to collapse
Yup.
Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
Click to expand...
Click to collapse
OK - I downloaded this and flashed it. Exactly the same as all the previous attempts. It appears to work, but when I restart, the phone is in exactly the same state as before, as if no flashing has happened.
Here is the command line output:
Code:
C:\>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.024s]
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.353s]
finished. total time: 0.380s
C:\>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.084s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.110s]
finished. total time: 1.197s
C:\>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.105s
C:\>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.360s]
writing 'boot'...
OKAY [ 0.670s]
finished. total time: 1.030s
C:\>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.695s]
finished. total time: 1.060s
C:\>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 8.140s]
writing 'system'...
OKAY [ 8.155s]
finished. total time: 16.295s
C:\>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.185s]
writing 'system'...
OKAY [ 8.690s]
finished. total time: 16.885s
C:\>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 8.265s]
writing 'system'...
OKAY [ 8.755s]
finished. total time: 121.145s
C:\>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 5.255s]
writing 'system'...
OKAY [ 6.475s]
finished. total time: 11.735s
C:\>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.605s]
writing 'modem'...
OKAY [ 0.825s]
finished. total time: 2.435s
C:\>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.020s
C:\>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.070s]
writing 'fsg'...
OKAY [ 3.180s]
finished. total time: 3.250s
C:\>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.025s]
finished. total time: 0.025s
C:\>mfastboot reboot
rebooting...
finished. total time: 0.005s
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Thanks again to all of you for your assistance in this matter.
IcyBee said:
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Click to expand...
Click to collapse
Recovery mode ADB will work in Linux. You could try side-loading the 5.0.2 OTA Update.

[Q] No sim card after trying to restore to stock

I need help. I was using KK and everything was working fine. So I installed lolipop xt1039 stock version, the sim and wifi werent working
So I did the update of the radio firmware and the wifi started working but the sim chip has not.
I tried everything... Wiped cache, data, dalvinik... still nothing makes the sim card work
I even tried going back to KK and reverting the radio firmware but even in KK the sim chip is not being recognized anymore.
I managed to install recovery TWRP-v2.8.3.0, the latest peregrin build that I found in this forum.
Made a full wipe, factory, data, you name it.
After this I installed android 4.4.4, 4.4.3...via fastboot
using the steps in this thread
http://forum.xda-developers.com/moto...kxb21-t2805619
And still no network. Wifi and gps works just fine, but no sim is detected.
The sim is working just fine, I tested it on other phone and it works. I also tested another sim chip that was working in my other phone into my moto g and no luck so far.
It could be you need to upgrade your Bootloader. I only suggest this as you appear to have tried everything else. On Moto G non-LTE this step is not necessary, but with Peregrine, things may be different.
This utility will allow you to upgrade to the XT1039 Lollipop Bootloader (v41.1A) - http://forum.xda-developers.com/moto-g/development/falcon-bootloader-upgrader-tool-t3093793
lost101 said:
It could be you need to upgrade your Bootloader. I only suggest this as you appear to have tried everything else. On Moto G non-LTE this step is not necessary, but with Peregrine, things may be different.
This utility will allow you to upgrade to the XT1039 Lollipop Bootloader (v41.1A) - http://forum.xda-developers.com/moto-g/development/falcon-bootloader-upgrader-tool-t3093793
Click to expand...
Click to collapse
Do you think its worth the risk of hardbricking?
flivon said:
Do you think its worth the risk of hardbricking?
Click to expand...
Click to collapse
The only hardbrick risk is if you start trying to flash the KitKat Bootloader afterwards.
lost101 said:
The only hardbrick risk is if you start trying to flash the KitKat Bootloader afterwards.
Click to expand...
Click to collapse
I don't think its a software problem, because I did everything one could do to try to reanimate his phone and still got nothing. Also, no one complained about having this problem when installing stock LP.
I updated the bootloader. Still the problem persists... I guess I will need to buy another phone :/
Question: Would using mfastboot instead of fastboot make a difference?
flivon said:
Would using mfastboot instead of fastboot make a difference?
Click to expand...
Click to collapse
Yes, always use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065​
There are many more things to try, do not give up yet.
lost101 said:
Yes, always use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065​
There are many more things to try, do not give up yet.
Click to expand...
Click to collapse
Tried again with mfastboot. Nothing
exactly same problem here.
SIM card doesn't see any services. Also, check that you can't dial 911 or 112 - it doesn't work!
Do either of you still have an IMEI number?
lost101 said:
Do either of you still have an IMEI number?
Click to expand...
Click to collapse
I have IMEI number....
lost101, if you can help:
http://forum.xda-developers.com/showpost.php?p=61704870&postcount=44
lost101 said:
Do either of you still have an IMEI number?
Click to expand...
Click to collapse
Yes, I have IMEI number too
Try this app: https://play.google.com/store/apps/details?id=com.sibbor.getril
Edit: Nevermind, app does not support Moto G.
Gosh, exactly the same issue. Was just going to create a new post. Here is what I wrote:
tl;dr: Location-UK. Rooted MotoG and installed CM11, found that the mobile network connectivity is gone. Flashed EU spec stock 5.0.2, still no luck. Status says Radio is off. What can I do to salvage it? (Still shows a valid IMEI). WiFi works fine.
@flivon - Is your phone originally XT1039 Retail EU?
XT1039 Retail EU 5.1 Radio: http://forum.xda-developers.com/devdb/project/dl/?id=13433
Use only the following commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
lost101 said:
@flivon - Is your phone originally XT1039 Retail EU?
XT1039 Retail EU 5.1 Radio: http://forum.xda-developers.com/devdb/project/dl/?id=13433
Use only the following commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
Click to expand...
Click to collapse
No. Its not. Its actually Brazilian retail. Also, trying to flash EU radio does not work.
@flivon - You can get more information about what is happening with radio by doing the following:
1) Dial: *#*#4636#*#*
2) Tap 'Phone information'
What is stated for:
GSM service
Network type
Also try turning radio off and on from this screen.
lost101 said:
@flivon - You can get more information about what is happening with radio by doing the following:
1) Dial: *#*#4636#*#*
2) Tap 'Phone information'
What is stated for:
GSM service
Network type
Also try turning radio off and on from this screen.
Click to expand...
Click to collapse
Turning radio on and off did nothing apparently
GSM service: Emergency calls only
Network type: Unknown
@flivon - Before trying anything else, I would like to see a mfastboot log of you flashing the Retail Brazil Firmware Image.
XT1040 Retail Brazil 5.1 Firmware Image: http://forum.xda-developers.com/showpost.php?p=61365158&postcount=592
lost101 said:
@flivon - Before trying anything else, I would like to see a mfastboot log of you flashing the Retail Brazil Firmware Image.
XT1040 Retail Brazil 5.1 Firmware Image: http://forum.xda-developers.com/showpost.php?p=61365158&postcount=592
Click to expand...
Click to collapse
The rom booted but still no sim card.
log:
Code:
C:\Users\Felipe\Desktop\fastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.042s]
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.365s]
finished. total time: 0.411s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.123s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.115s]
finished. total time: 1.240s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.069s]
writing 'logo'...
OKAY [ 0.076s]
finished. total time: 0.146s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.389s]
writing 'boot'...
OKAY [ 0.732s]
finished. total time: 1.124s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.729s]
finished. total time: 1.132s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257719 KB)...
OKAY [ 8.682s]
writing 'system'...
OKAY [ 11.477s]
finished. total time: 20.163s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257506 KB)...
OKAY [ 8.696s]
writing 'system'...
OKAY [ 10.234s]
finished. total time: 18.933s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (255259 KB)...
OKAY [ 8.583s]
writing 'system'...
OKAY [ 15.590s]
finished. total time: 24.178s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (189925 KB)...
OKAY [ 6.429s]
writing 'system'...
OKAY [ 9.097s]
finished. total time: 15.529s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60232 KB)...
OKAY [ 2.073s]
writing 'modem'...
OKAY [ 1.618s]
finished. total time: 3.695s
C:\Users\Felipe\Desktop\fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.023s
C:\Users\Felipe\Desktop\fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.023s]
finished. total time: 0.024s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (661 KB)...
OKAY [ 0.070s]
writing 'fsg'...
OKAY [ 5.674s]
finished. total time: 5.747s
C:\Users\Felipe\Desktop\fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.338s]
finished. total time: 0.339s
C:\Users\Felipe\Desktop\fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 3.870s]
finished. total time: 3.871s
C:\Users\Felipe\Desktop\fastboot>mfastboot reboot
rebooting...
finished. total time: 0.003s
flivon said:
The rom booted but still no sim card.
log:
<snip>
Click to expand...
Click to collapse
Fastboot log looks good. I still think you should try a brand new SIM.
EDIT: Maybe even unlock phone to all networks if not already done. Doing so may trigger a hardware change.

Bricked while Downgrading to Lollipop

Hey , Guyz ... So i have Xt1550 ( Moto G 2015 Indian - 2GB / 16 GB )
Updated to Marshmallow and i didn't liked it that much so , tried of Downgrading by flashing factory images of Android 5.1.1 Lollipop
( http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 )
I used this command on fastboot -
Code:
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 reboot
Cmd commands -
Code:
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.063s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.531s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.714s]
finished. total time: 1.902s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.219s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.328s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.720s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.388s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.751s]
writing 'recovery'...
OKAY [ 1.047s]
finished. total time: 1.799s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (232264 KB)...
OKAY [ 8.355s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.022s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (261326 KB)...
OKAY [ 9.178s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.305s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (241145 KB)...
OKAY [ 8.747s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.872s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (255386 KB)...
OKAY [ 9.354s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.526s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (257385 KB)...
OKAY [ 9.151s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.231s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (240406 KB)...
OKAY [ 8.585s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.710s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36944 KB)...
OKAY [ 1.555s]
writing 'modem'...
OKAY [ 1.064s]
finished. total time: 2.635s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.086s]
finished. total time: 0.086s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.116s]
finished. total time: 0.116s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2035 KB)...
OKAY [ 0.243s]
writing 'fsg'...
OKAY [ 0.113s]
finished. total time: 0.359s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.140s]
finished. total time: 0.140s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 4.068s]
finished. total time: 4.084s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot reboot
rebooting...
finished. total time: -0.000s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>
So now my phone is bricked ! thats my fault as i tried downgrading bootloader !
I can access bootloader mode and i have already tried flashing that again without using
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
commands !
Now tell me what to do , I don't want to unlock bootloader and install twrp and install cm12.1.1
Please help what can be done ?
Thanks
This is because your BL is locked. Pls unlock it and then try flashing the firmware. BROTIP: Always avoid downgrading.. Now flash the MM firmware to at least boot the device (if firmware is out).
Forever Alone said:
This is because your BL is locked. Pls unlock it and then try flashing the firmware. BROTIP: Always avoid downgrading.. Now flash the MM firmware to at least boot the device (if firmware is out).
Click to expand...
Click to collapse
Even i can't unlock bootloader .. because i have not enabled that on developer settings ( - As said by nelsonw )
harsinghal said:
Even i can't unlock bootloader [emoji14] .. because i have not enabled that on developer settings ( - As said by nelsonw )
Click to expand...
Click to collapse
Call it Stone not brick....[emoji12]
Sent from my MotoG3 using Tapatalk
get someone to backup their bootloader.img from marshmallow , and restore it back to YOUR device . that should work. I dont personally have marshmallow on my device as it is not available yet
ifu said:
Call it Stone not brick....[emoji12]
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Brick can be bricked , stone is hard to break !
I can deal with a brick ... not with a stone
therealduff1 said:
get someone to backup their bootloader.img from marshmallow , and restore it back to YOUR device . that should work. I dont personally have marshmallow on my device as it is not available yet
Click to expand...
Click to collapse
You know any guide on how to backup bootloader image ? I can try asking my frnd for that !
harsinghal said:
You know any guide on how to backup bootloader image ? I can try asking my frnd for that !
Click to expand...
Click to collapse
You can try googling it , as I am not sure myself. But I do know it is do able. Probably someone like fastboot backup bootloader. Don't try that command because I don't actually know if that it right xD . Anyway just flash the output file as a .img file , to your device and it should all be ok.
Please hit thanks , it means alot
Whether downgradable?
Fellas I have an XT1550. I got updated to stock MM via OTA. Afterwards I unlocked my bootloade, flashed latest TWRP and BetaSuperSU 2.66. Everything was fine untill when I tried to remove my Bootloader Unlocked warning screen by following steps in http://forum.xda-developers.com/2015-moto-g/themes-apps/remove-unlocke-bootloader-message-t3177801.
My phone got stuck in bootloader screen.
I wiped everything using TWRP.
Is it safe for me to flash stock lollipop now using fastboot without hard bricking.??????
Help !
Still Not able to Downgrade to Lollipop ! :crying::crying:
jithgr said:
Fellas I have an XT1550. I got updated to stock MM via OTA. Afterwards I unlocked my bootloade, flashed latest TWRP and BetaSuperSU 2.66. Everything was fine untill when I tried to remove my Bootloader Unlocked warning screen by following steps in http://forum.xda-developers.com/2015-moto-g/themes-apps/remove-unlocke-bootloader-message-t3177801.
My phone got stuck in bootloader screen.
I wiped everything using TWRP.
Is it safe for me to flash stock lollipop now using fastboot without hard bricking.??????
Click to expand...
Click to collapse
I upgraded to MM and downgraded to 5.1.1 successfully.
1> Try to access your stock recovery and do a wipe (data and cache). This step is very important as stated by @lost101 on his firmware flashing guide.
2> reboot back to boot loader mode
3> when using the flash commands, the first one : fastboot flash partition gpt.bin will potentially fail. This is since the partitions were updated to the tables defined according to the requirement of MM. Dont worry. fail on this command wont do anything.
4> proceed with the other commands one by one to flash your 5.1.1 carefully until the last command which says reboot.
TaDa.. downgrade completed.
'Factory data reset' in Android is an essential step that needs to be done when changing ROMs or downgrading. If your bootloader is unlocked, flash a custom ROM via TWRP, boot into Android and do a reset. After this, fastboot flashing of firmware images will be successful. If your bootloader is locked, you may have no choice but to return the phone to retailer.
@harsinghal :
Try the below order. It worked for me.
fastboot flash partition gpt.bin (Skip this command if prev validation fails)
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 reboot
Click to expand...
Click to collapse
Thanks bro, after data and cache wipe it worked, until then it was a nightmare.
Thanks again.

Soft Brick with Locked Booloader in Moto g3 XT1550 (Dual-SIM)

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)

Allow OEM Unlock Bootloader

Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!
axbom said:
Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!
Click to expand...
Click to collapse
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.
acejavelin said:
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.
Click to expand...
Click to collapse
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!
axbom said:
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!
Click to expand...
Click to collapse
Did you factory default prior to flashing? That is a required step...
acejavelin said:
Did you factory default prior to flashing? That is a required step...
Click to expand...
Click to collapse
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..
axbom said:
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..
Click to expand...
Click to collapse
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk
acejavelin said:
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_set
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>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.708s]
finished. total time: 0.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>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.551s]
finished. total time: 1.645s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.125s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.519s]
writing 'boot'...
OKAY [ 0.936s]
finished. total time: 1.471s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 1.486s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (243355 KB)...
OKAY [ 7.717s]
writing 'system'...
OKAY [ 8.975s]
finished. total time: 16.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (233538 KB)...
OKAY [ 7.478s]
writing 'system'...
OKAY [ 7.597s]
finished. total time: 15.092s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (256922 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 8.308s]
finished. total time: 16.521s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (257262 KB)...
OKAY [ 8.198s]
writing 'system'...
OKAY [ 8.303s]
finished. total time: 16.500s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (255507 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 8.575s]
finished. total time: 16.717s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (258021 KB)...
OKAY [ 8.225s]
writing 'system'...
OKAY [ 8.266s]
finished. total time: 16.507s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (210541 KB)...
OKAY [ 6.716s]
writing 'system'...
OKAY [ 11.695s]
finished. total time: 18.410s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.165s]
writing 'modem'...
OKAY [ 0.974s]
finished. total time: 2.155s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>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\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>
From what I can see it all looks fine?
axbom said:
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
...
From what I can see it all looks fine?
Click to expand...
Click to collapse
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?
acejavelin said:
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?
Click to expand...
Click to collapse
After issuing the reboot command at the end it goes to the white screen with the motorola logo, then the screen goes black, and then back to the motorola logo, and keep on going like that.
Yeah that's correct, 0-6 sparsechunk files. I did fastboot ERASE cache and ERASE userdata, since I can't get into the recovery menu (goes into bootloop if I try). When I try any of those commands it says Formatting is not supported for filesystem with type 'raw'.
im having the exact same problem, used the same software and carried out the same steps as you with no luck either.
from what ive read its because you need to wipe all the data first but because we get the, cant its RAW message, it wont download the firmware onto the phone even though it says it went ok. at the minute i havnt found anyone whos successfully been able to repair this fault.
mine was working perfectly untill the ota update
There is no fix for that, use your warranty if you have so
Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.
yobac said:
Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.
Click to expand...
Click to collapse
Contact Moto directly via their website.
Sent from my MotoG3 using Tapatalk
1st Flash via Adb !
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !
FaizanChauhaan said:
1st Flash via Adb !
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !
Click to expand...
Click to collapse
It's fastboot not adb lol. Contradictory sentences
Edit: BTW motoboot.img is not present, it may refer to earlier generation of moto g. There is an line to flash bootloader.img instead. Have a look here : http://forum.xda-developers.com/showthread.php?t=3187750. Thanks.
Broadcasted from Zeta Reticuli

Categories

Resources