Flashing NON-GPE stock problem - Moto G Q&A, Help & Troubleshooting

Hello there guys! I'll resume my history.
So this was me one month after buying the Motorola Moto G XT1032 8GB, unlocking the bootloader without any problems So I wasn't really into the device info and didn't know about a GPE. So I downloaded a folder with a couple of images and .bin files and excuted a .bat inside the folder that turned my Stock 4.4.4 into Stock 4.4.2 GPE. After first reboot I just installed Paranoid Android and didn't come back to stock since then (a few months back).
Now I tried to go back to stock NON-GPE flashing "Android 4.3 Blur_Version.14.71.8.falcon_umts.Latam.en.AR" and "Android 4.4.2 Blur_Version.173.44.9.falcon_umts.Latam.en.AR" with this method GUIDE] Moto G - Restore stock firmware and I got this two errors in both of the cases:
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.030s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.363s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.405s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (619 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.161s]
finished. total time: 0.240s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.378s]
writing 'boot'...
OKAY [ 1.124s]
finished. total time: 1.502s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.379s]
writing 'recovery'...
OKAY [ 1.237s]
finished. total time: 1.617s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (256840 KB)...
OKAY [ 8.098s]
writing 'system'...
OKAY [ 17.707s]
finished. total time: 25.805s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (243300 KB)...
OKAY [ 7.668s]
writing 'system'...
OKAY [ 14.775s]
finished. total time: 22.443s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (219577 KB)...
OKAY [ 6.920s]
writing 'system'...
OKAY [ 23.237s]
finished. total time: 30.157s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47104 KB)...
OKAY [ 1.526s]
writing 'modem'...
OKAY [ 2.332s]
finished. total time: 3.859s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.070s]
finished. total time: 0.070s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.137s]
finished. total time: 0.137s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (107 KB)...
OKAY [ 0.082s]
writing 'fsg'...
OKAY [ 5.303s]
finished. total time: 5.385s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml#
Click to expand...
Click to collapse
You see? I got error with gtp.bin and motoboot.img but I kept flashing to see where that would take me. It turned out to take me witha bootloop Never going further than logo.
So what did I do? I ran that GPE 4.4.2 I flashed the first time I unlocked my bootloader. And it was alive again, booting like a charm. Now on crDroid again.
And my question is: what happened? Why am I able to flash a GPE 4.4.2 but not a Latam stock Retail for my country (Argentina)? I don't get it. I flashed from Windows and Ubuntu, with differents fastboot files, with mfasboot given in that Tutorial but nothing worked except turning it into a GPE Moto G.
Any contribution will be helpful, still want to go to stock Moto G. Cheers.

XXtremiXX said:
Hello there guys! I'll resume my history.
So this was me one month after buying the Motorola Moto G XT1032 8GB, unlocking the bootloader without any problems So I wasn't really into the device info and didn't know about a GPE. So I downloaded a folder with a couple of images and .bin files and excuted a .bat inside the folder that turned my Stock 4.4.4 into Stock 4.4.2 GPE. After first reboot I just installed Paranoid Android and didn't come back to stock since then (a few months back).
Now I tried to go back to stock NON-GPE flashing "Android 4.3 Blur_Version.14.71.8.falcon_umts.Latam.en.AR" and "Android 4.4.2 Blur_Version.173.44.9.falcon_umts.Latam.en.AR" with this method GUIDE] Moto G - Restore stock firmware and I got this two errors in both of the cases:
You see? I got error with gtp.bin and motoboot.img but I kept flashing to see where that would take me. It turned out to take me witha bootloop Never going further than logo.
So what did I do? I ran that GPE 4.4.2 I flashed the first time I unlocked my bootloader. And it was alive again, booting like a charm. Now on crDroid again.
And my question is: what happened? Why am I able to flash a GPE 4.4.2 but not a Latam stock Retail for my country (Argentina)? I don't get it. I flashed from Windows and Ubuntu, with differents fastboot files, with mfasboot given in that Tutorial but nothing worked except turning it into a GPE Moto G.
Any contribution will be helpful, still want to go to stock Moto G. Cheers.
Click to expand...
Click to collapse
Do this at your own risk:
If your phone is a gsm xt1032 then grab a EU(european) 4.4.4 stock firmware and flash that via fastboot. Should work...
If not then try flashing a custom recovery like twrp or clockworkmod. Grab the EU or US 4.4.4 untouched from this link: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and flash it via recovery.

Related

[Q] Unable to flash ROMS/OTA updates

I received my OnePlus One a few days ago and attempted install the 05q OTA update, however when the phone rebooted it was stuck in a bootloop where various artifacts would appear on screen before rebooting. I managed to flash back to the 44s firmware via fastboot and install TWRP and root the device.
I have tried to update the firmware via fastboot and TWRP but each time it ends up bootlooping. I have also tried to flash the CM12 nightlys, and although the install is successful, the same issue is present when trying to boot. Attempting to flash different kernels (eg. Franco kernel) has the same issues.
I'm not sure if this is a common problem or if I've just managed to get a dud phone. The phone I received seems to be the Chinese variant (Missing LTE bands), but it arrived with CM11S installed. Not sure if that would affect the ability to update?
Any help or information would be much appreciated
You shouldn't have any problems flashing regardless of which variant you have. Are you checking the md5 of downloaded files before flashing? Which firmware did you try to update? Saying "the firmware" is like saying nothing at all. Are you remembering to wipe properly before flashing CM12? Which version of which kernel was flashed on which ROM? There's a theme here, please provide more detailed information.
My first attempt was the OTA update from XNPH44S to XNPH05Q. This caused the device to get stuck at the OnePlus logo.
Then I proceeded to unlock the bootloader and attempt to flash the 05Q fastboot image located at http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746. It's appears to have successfully installed, but again, bootloops.
Flashing the 44S update from the link above worked.
As for CM12, a factory reset was performed before attempting to flash the cm-12-20150121-UNOFFICIAL-bacon.zip found here https://basketbuild.com/devs/klvnhng/cm-12.0_bacon. Successful install, but bootlooping persists.
Attempted to flash Franco kernel r35 found here http://kernels.franco-lnx.net/OnePlusOne/4.4/ over stock XNPH44S firmware. No luck.
If any more information is required do not hesitate to ask.
That all looks fine, except for the factory reset before flashing CM12. You really need a full wipe when changing ROMs like that, a full wipe consists of wiping system, data, cache, and dalvik cache. It seems odd that after flashing the stock images you'd end up in a bootloop. So when you say flashing the 44S update worked, you mean you flashed the 44S stock images with fastboot and the phone booted up and operated normally?
timmaaa said:
That all looks fine, except for the factory reset before flashing CM12. You really need a full wipe when changing ROMs like that, a full wipe consists of wiping system, data, cache, and dalvik cache. It seems odd that after flashing the stock images you'd end up in a bootloop. So when you say flashing the 44S update worked, you mean you flashed the 44S stock images with fastboot and the phone booted up and operated normally?
Click to expand...
Click to collapse
Correct. If I flash 44S the phone will boot normally, but if I try any other images (eg 05Q) it gets stuck.
samskies1 said:
Correct. If I flash 44S the phone will boot normally, but if I try any other images (eg 05Q) it gets stuck.
Click to expand...
Click to collapse
If you decide to make another attempt to flash the 05Q stock images, please copy/paste the text from the command prompt here do I can see.
Transmitted via Bacon
timmaaa said:
If you decide to make another attempt to flash the 05Q stock images, please copy/paste the text from the command prompt here do I can see.
Transmitted via Bacon
Click to expand...
Click to collapse
C:\Users\Samus\Desktop\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.782s]
writing 'modem'...
OKAY [ 1.243s]
finished. total time: 3.025s
C:\Users\Samus\Desktop\adb>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ -0.000s]
writing 'dbi'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Samus\Desktop\adb>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ -0.000s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.313s]
writing 'LOGO'...
OKAY [ 0.212s]
finished. total time: 0.525s
C:\Users\Samus\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.328s]
writing 'oppostanvbk'...
OKAY [ 0.234s]
finished. total time: 0.563s
C:\Users\Samus\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5956 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.328s
C:\Users\Samus\Desktop\adb>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (10432 KB)...
OKAY [ 0.328s]
writing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.954s
C:\Users\Samus\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7854 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.422s
C:\Users\Samus\Desktop\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.332s]
sending sparse 'system' (524108 KB)...
OKAY [ 18.747s]
writing 'system'...
OKAY [ 23.967s]
sending sparse 'system' (320781 KB)...
OKAY [ 11.519s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 70.597s
C:\Users\Samus\Desktop\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 3.751s]
sending 'userdata' (141075 KB)...
OKAY [ 4.436s]
writing 'userdata'...
OKAY [ 13.012s]
finished. total time: 21.199s
C:\Users\Samus\Desktop\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>
samskies1 said:
C:\Users\Samus\Desktop\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.782s]
writing 'modem'...
OKAY [ 1.243s]
finished. total time: 3.025s
C:\Users\Samus\Desktop\adb>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ -0.000s]
writing 'dbi'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Samus\Desktop\adb>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ -0.000s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.313s]
writing 'LOGO'...
OKAY [ 0.212s]
finished. total time: 0.525s
C:\Users\Samus\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.328s]
writing 'oppostanvbk'...
OKAY [ 0.234s]
finished. total time: 0.563s
C:\Users\Samus\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5956 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.328s
C:\Users\Samus\Desktop\adb>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (10432 KB)...
OKAY [ 0.328s]
writing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.954s
C:\Users\Samus\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7854 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.422s
C:\Users\Samus\Desktop\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.332s]
sending sparse 'system' (524108 KB)...
OKAY [ 18.747s]
writing 'system'...
OKAY [ 23.967s]
sending sparse 'system' (320781 KB)...
OKAY [ 11.519s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 70.597s
C:\Users\Samus\Desktop\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 3.751s]
sending 'userdata' (141075 KB)...
OKAY [ 4.436s]
writing 'userdata'...
OKAY [ 13.012s]
finished. total time: 21.199s
C:\Users\Samus\Desktop\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>
Click to expand...
Click to collapse
That all looks fine. But it's not booting correctly still?
Transmitted via Bacon
timmaaa said:
That all looks fine. But it's not booting correctly still?
Transmitted via Bacon
Click to expand...
Click to collapse
Still no luck unfortunately. This is it attempting to boot imgur.com/LIT8i5S (Apologies for the low quality. Using old phone)
samskies1 said:
Still no luck unfortunately. This is it attempting to boot imgur.com/LIT8i5S (Apologies for the low quality. Using old phone)
Click to expand...
Click to collapse
Well I'm stumped, usually the stock images are the thing that revive a One from issues like this. I think it's time to contact the seller and claim warranty.
Transmitted via Bacon
---------- Post added at 07:29 ---------- Previous post was at 07:13 ----------
Edit:
Actually, it's early, I forgot about these, give them a try:
http://forum.xda-developers.com/showthread.php?t=2991851
Unbrick Tool
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And then try flashing 05Q.
Transmitted via Bacon
timmaaa said:
Well I'm stumped, usually the stock images are the thing that revive a One from issues like this. I think it's time to contact the seller and claim warranty.
Transmitted via Bacon
---------- Post added at 07:29 ---------- Previous post was at 07:13 ----------
Edit:
Actually, it's early, I forgot about these, give them a try:
http://forum.xda-developers.com/showthread.php?t=2991851
Unbrick Tool
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And then try flashing 05Q.
Transmitted via Bacon
Click to expand...
Click to collapse
Tried the second method you linked. No luck I'm afraid. Attempted the OTA and via fastboot.
samskies1 said:
Tried the second method you linked. No luck I'm afraid. Attempted the OTA and via fastboot.
Click to expand...
Click to collapse
I can't think of why that's happening, you might need to RMA.
Transmitted via Bacon
timmaaa said:
I can't think of why that's happening, you might need to RMA.
Transmitted via Bacon
Click to expand...
Click to collapse
I've sent in a return request.
If you don't mind me asking, did you acquire your phone from OnePlus directly? Or buy through a third party seller?
I only ask because I am also an Australian, and I am unable to purchase from the OnePlus website, due to a lack of shipping to Australia.
samskies1 said:
I've sent in a return request.
If you don't mind me asking, did you acquire your phone from OnePlus directly? Or buy through a third party seller?
I only ask because I am also an Australian, and I am unable to purchase from the OnePlus website, due to a lack of shipping to Australia.
Click to expand...
Click to collapse
I purchased directly from OnePlus, and I know dozens of other Australians who did so. We used freight forwarding companies like Shipito, they provide you with an American mailing address and then forward it on to you. I think it cost me an extra $35 on top of the cost of the phone.
Transmitted via Bacon
timmaaa said:
I purchased directly from OnePlus, and I know dozens of other Australians who did so. We used freight forwarding companies like Shipito, they provide you with an American mailing address and then forward it on to you. I think it cost me an extra $35 on top of the cost of the phone.
Transmitted via Bacon
Click to expand...
Click to collapse
If this return to a third party seller goes though I think I may use that method to buy one directly from OnePlus.
I have similar problem, can't update official firmware through ota or manually installation, but my phone still manage to flash 3rd party roms and Calculkin's rooted 05q rom...??
johnsin5393 said:
I have similar problem, can't update official firmware through ota or manually installation, but my phone still manage to flash 3rd party roms and Calculkin's rooted 05q rom...
Click to expand...
Click to collapse
What happens when you try to flash official firmware?
Yeah I'm going to give Calkulin's rom a try when I get home from work.
samskies1 said:
What happens when you try to flash official firmware?
Yeah I'm going to give Calkulin's rom a try when I get home from work.
Click to expand...
Click to collapse
In cyanogen recovery, I couldn't flash firmware update or others zip file... Only after flashed Calkulin's packed zip, then I could flash to 05q
johnsin5393 said:
In cyanogen recovery, I couldn't flash firmware update or others zip file... Only after flashed Calkulin's packed zip, then I could flash to 05q
Click to expand...
Click to collapse
Would you happen to have a link to what you flashed?

XT1032 - unable to run system

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...

OnePlus One Stuck In Bootloop After Flashing CyanogenMod From OxygenOS

HI.
recently ive want to install ubuntu touch on my opo but i cant. then i want to roll back into the cyanogen os and its stuck on cyanogen boot animation. i just can install oxygen os that i hate it!
please help me to roll back into the cyanogen os 12.1
files i have download
modem :YNG1TAS0YL_Extras.zip
Full-oxygen-04-04-15-Bacon-modem-flashable.zip
XNPH33R_Extras.zip
roms : cm-12.0-YNG1TAS17L-bacon-signed.zip
cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip
oxygenos_1.0.0
i use ubuntu on my pc
my recovery is twrp
dirtylife2011 said:
HI.
recently ive want to install ubuntu touch on my opo but i cant. then i want to roll back into the cyanogen os and its stuck on cyanogen boot animation. i just can install oxygen os that i hate it!
please help me to roll back into the cyanogen os 12.1
files i have download
modem :YNG1TAS0YL_Extras.zip
Full-oxygen-04-04-15-Bacon-modem-flashable.zip
XNPH33R_Extras.zip
roms : cm-12.0-YNG1TAS17L-bacon-signed.zip
cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip
oxygenos_1.0.0
i use ubuntu on my pc
my recovery is twrp
Click to expand...
Click to collapse
Flash the stock images with fastboot. See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
PS. It's the "cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip" one that you'll use.
Heisenberg said:
Flash the stock images with fastboot. See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
PS. It's the "cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip" one that you'll use.
Click to expand...
Click to collapse
I use that thread to flash my phone and install both of YNG1TAS2I3 and next ver YOG...-fastboot.ZIP and its stuck on logo . then i flash both version for recovery and its stuck on logi again. Help me
dirtylife2011 said:
I use that thread to flash my phone and install both of YNG1TAS2I3 and next ver YOG...-fastboot.ZIP and its stuck on logo . then i flash both version for recovery and its stuck on logi again. Help me
Click to expand...
Click to collapse
Please try again and copy/paste the text from the command prompt here so I can see.
Heisenberg said:
Please try again and copy/paste the text from the command prompt here so I can see.
Click to expand...
Click to collapse
here you are.
Code:
~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.682s]
writing 'modem'...
OKAY [ 0.962s]
finished. total time: 3.644s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.018s]
finished. total time: 0.031s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.003s]
writing 'dbi'...
OKAY [ 0.011s]
finished. total time: 0.014s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.020s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.035s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.017s]
finished. total time: 0.026s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.015s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.029s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.028s]
finished. total time: 0.043s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.476s]
writing 'oppostanvbk'...
OKAY [ 0.188s]
finished. total time: 0.665s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (6494 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.121s]
finished. total time: 0.422s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.107s]
sending 'cache' (10432 KB)...
OKAY [ 0.485s]
writing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.810s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9120 KB)...
OKAY [ 0.425s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.594s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.402s]
sending 'system' (1034756 KB)...
OKAY [ 47.980s]
writing 'system'...
OKAY [ 22.148s]
finished. total time: 70.530s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.516s]
sending 'userdata' (141075 KB)...
OKAY [ 6.575s]
writing 'userdata'...
OKAY [ 3.205s]
finished. total time: 13.297s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot reboot
rebooting...
dirtylife2011 said:
here you are.
Code:
~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.682s]
writing 'modem'...
OKAY [ 0.962s]
finished. total time: 3.644s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.018s]
finished. total time: 0.031s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.003s]
writing 'dbi'...
OKAY [ 0.011s]
finished. total time: 0.014s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.020s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.035s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.017s]
finished. total time: 0.026s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.015s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.029s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.028s]
finished. total time: 0.043s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.476s]
writing 'oppostanvbk'...
OKAY [ 0.188s]
finished. total time: 0.665s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (6494 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.121s]
finished. total time: 0.422s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.107s]
sending 'cache' (10432 KB)...
OKAY [ 0.485s]
writing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.810s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9120 KB)...
OKAY [ 0.425s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.594s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.402s]
sending 'system' (1034756 KB)...
OKAY [ 47.980s]
writing 'system'...
OKAY [ 22.148s]
finished. total time: 70.530s
[email protected]alihk-VPCEB3MFX:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.516s]
sending 'userdata' (141075 KB)...
OKAY [ 6.575s]
writing 'userdata'...
OKAY [ 3.205s]
finished. total time: 13.297s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot reboot
rebooting...
Click to expand...
Click to collapse
Hmm, can you boot into recovery?
Heisenberg said:
Hmm, can you boot into recovery?
Click to expand...
Click to collapse
yes .now its boot to cyanogen recovery
dirtylife2011 said:
yes .now its boot to cyanogen recovery
Click to expand...
Click to collapse
Ok, you can flash one of the official zips. You already have this one:
cm-12.0-YNG1TAS17L-bacon-signed.zip
So flash that with the stock recovery.
Heisenberg said:
Ok, you can flash one of the official zips. You already have this one:
cm-12.0-YNG1TAS17L-bacon-signed.zip
So flash that with the stock recovery.
Click to expand...
Click to collapse
only when i install cyanogen it says "patching system unconditionaly...."
is that okay??
and its not work again.
dirtylife2011 said:
only when i install cyanogen it says "patching system unconditionaly...."
is that okay??
and its not work again.
Click to expand...
Click to collapse
Yes that message is normal. Did the flash succeed or fail?
deleted
Heisenberg said:
Yes that message is normal. Did the flash succeed or fail?
Click to expand...
Click to collapse
in cyanogen recovery there is no message that its succeed or failed
but in twrp its succeed.
but all of installation section is already up to date. and its done very fast!
dirtylife2011 said:
in cyanogen recovery there is no message that its succeed or failed
but in twrp its succeed.
but all of installation section is already up to date. and its done very fast!
Click to expand...
Click to collapse
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Heisenberg said:
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Click to expand...
Click to collapse
thank you for step by step help....
and sorry for my bad English language
Heisenberg said:
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Click to expand...
Click to collapse
Its Worked!!!
Thanks!!!
Its The final Way
In my country We call adept final impact
dirtylife2011 said:
Its Worked!!!
Thanks!!!
Its The final Way
In my country We call adept final impact
Click to expand...
Click to collapse
Oh hell yeah!! Awesome news
Thank you so much for this guide to fixing a corrupt persist.img. I just learned how to use cmd.exe and fastboot to flash this to my phone that was messed up. This guide saved my phone!!

How can i make my moto g dual sim again...

Hi this is my first request for help ever, have tired almost all roms available on xda
I never needed to touch my rom till was on kitkat, i had heard the hole world crying for bugs with kitkat but my phone never reported any major bug (i had not even rooted my phone) then came the curse LOLIPOP 5.02 there were two things that made me force to unlock bootloader 1> slow 2nd> ghost windows showing up in taskbar
from the day i flashed to stock rom kitkat 4.4.4 us retail (xt1032) availabe on xda forum i lost my second sim working
till this date i have flashed endless roms even cwm 12 and all versions of stock for asian retail have not tried flashing and brazil fimware.
it just doesn't detect if any sim is inserted.
i have tried the stock radio thread for kitkat 4.4.4 , 5.02, 5.1 none of them work.
If anyone is having moto g xt1033 indian stock rom with dual sim working
can you please send me a screen shot of about section in settings
i want to check what baseband version you guys are having
one last thing i had made a backup using cynogen recovery but on restoring the backup my moto g never boots it was of stock lolipop can anyone help in this regards..
currently am on stock lolipop 5.1
my baseband version is MSM8626BP_1032.3116.98.00R EMEA_DSDS_CUST
i think 1032 in above baseband means radio of xt1032 while i need 1033 (i guess)
i have updated using indian ota update of stock rom using stock recovery.
Issue still persists sim 2 not detected, both sims used to work before flashing any firware manually.
Simply flash the latest XT1033 Retail Asia 5.1 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide a log of the flashing process if this does not resolve your problem. Copy and paste the contents of Command Prompt. Take screen-shots if necessary.
edit: above method
new problem
i did as you said, this is first time i will be flashing 5.1 directly my system was already on 5.1 and now system is not booting did system userdata wipe and cache wipe
i flahed this file XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7 and the phone keeps stuck on bootloader logo
bootloader version is 41.1A
i can enter fastboot and am thinking of going back to 5.02 cannot enter recovery (stock)
now am flashing ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip i dont think 2nd sim will work but at least working system.
still if anyone has both sims working do tell me your baseband version
thank you..
here is the log
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
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.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
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.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>
huzeifa88 said:
i did as you said, this is first time i will be flashing 5.1 directly my system was already on 5.1 and now system is not booting did system userdata wipe and cache wipe
i flahed this file XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7 and the phone keeps stuck on bootloader logo
bootloader version is 41.1A
i can enter fastboot and am thinking of going back to 5.02 cannot enter recovery (stock)
now am flashing ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip i dont think 2nd sim will work but at least working system.
still if anyone has both sims working do tell me your baseband version
thank you..
here is the log
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
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.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
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.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>
Click to expand...
Click to collapse
now flashed 5.02 and it too just shows me the boot logo saying warning bootloader unlocked nothing else is happening getting a little tense now log for 5.02
C:\adb>flash.bat
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
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.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
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.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>
Please stop trying different Firmware Images. Only do as directed for your own safety.
Edit: Manually type commands, do not use a .bat file or script. Skip the command related to motoboot.img - repeatedly flashing the Bootloader is dangerous and completely unnecessary.
Type the following command before any other:
mfastboot oem unlock​
lost101 said:
Please stop trying different Firmware Images. Only do as directed for your own safety.
Click to expand...
Click to collapse
well i did try to flash 5.1 image twice its not working nor is the 5.02 any ideas just stays on the boot logo the simple static one not the animated one.
bootleoader version is 41.1A system is 5.02
huzeifa88 said:
well i did try to flash 5.1 image twice its not working nor is the 5.02 any ideas just stays on the boot logo the simple static one not the animated one.
Click to expand...
Click to collapse
now am on 5.02 boot loader version is same as 5.1 does it need to downgrade.
huzeifa88 said:
now am on 5.02 boot loader version is same as 5.1 does it need to downgrade.
Click to expand...
Click to collapse
Stop flashing / messing with the Bootloader. Period. You will end up with a dead phone.
Finally back from dead
I flashed kitkat stock rom without trying to downgrade boot loader as i knew it could brick my phone and just as usual phone did not boot past boot logo of boot recovery stating boot loader unlocked...
but my luck turned kitkat stock rom recovery started to work without wasting time i flashed twrp recovery over kitkat stock recovery
once twrp i flashed cm12 last stable built volla cm12 booted
now still only one sim will work but i guess i had enough experiments i had once tried the donkey kernel on cm12 it never booted. so lets forget dual sim.
please dont recommend anyone to flash 5.1 stock rom i has some bug never boots or maybe coz i already had 5.1 installed using ota method.
@huzeifa88 - You are going to destroy your phone. I have tried to help you, but you ignore what I say.
Do not flash old Firmware Images and then accept an OTA Update. Your phone will switch off and never turn on again. I have already warned you to stop trying random Firmware Images.
phone doesnt boot on 5.1 had no options
I did flash the 5.1 lolipop image but phone did not boot it would just kept stuck at bootloader spash image (White color image saying boot loader unlocked) and did not reach the motorola animated boot screen
I left it there for around 30 mins after which i was sure its not gonna boot
Again even tried deleting all data and cache using fastboot command
even the recovery would not open it would stay on the bootloader splah screen
what i am experiancing with this phone is rare and happened 1st time maybe all those who have updated their boot loader should not mess with there cell anymore
anyway all is GOOD now i am HAPPLY using CM12 ROM and am never gonna flash any stock rom 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)

Categories

Resources