Database Users

[Q] Can i downgrade from 6.0.1 to 6.0 or even LP?

I have a turbo 2 and i was wondering if i can downgrade it to an earlier version?
my bootloader is showing A8.56 (sha-09a6e4e, 2015 - 11 - 13)
baseband: M8994_1255339.41.01.94.O1R KINZIE_VZW_CUST
thanks

Yes, you can. I've downgraded from 6.0.1 to 5.1.1.
Not sure if you want a unlocked bootlader to downgrade.

do you got a link to the firmware? did you have bootloader unlocked?

rodrigo196 said:
Yes, you can. I've downgraded from 6.0.1 to 5.1.1.
Not sure if you want a unlocked bootlader to downgrade.
Click to expand...
Click to collapse
for anyone else wondering you cannot downgrade from 6.0.1 to 5.1.1, dont know this guy said you can
c:\mfastboot-v2>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2781 KB)...
OKAY [ 0.070s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing pmic ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing sdi ...
OKAY [ 1.442s]
finished. total time: 1.514s
c:\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (40960 KB)...
OKAY [ 0.930s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.579s

I would guess he has an X-Force since he mentioned unlocking the bootloader...

mjones73 said:
I would guess he has an X-Force since he mentioned unlocking the bootloader...
Click to expand...
Click to collapse
Yes, mine is a Moto X Force with unlocked bootloader. Works fine

rodrigo196 said:
Yes, mine is a Moto X Force with unlocked bootloader. Works fine
Click to expand...
Click to collapse
This is so confusing to have the same forum for both devices , since they differ much in terms of root accessibility and bootloader unlock as well.

rodrigo196 said:
Yes, you can. I've downgraded from 6.0.1 to 5.1.1.
Click to expand...
Click to collapse
Just to make sure I don't understand wrong: You do have an X force with locked bootloader and downgraded it from 6.0.1 to 5.1.1? How can this be done? Are OTA updates working after the upgrade? I read that downgrading the bootloader will brick the device.

truwrxtacy said:
for anyone else wondering you cannot downgrade from 6.0.1 to 5.1.1, dont know this guy said you can
c:\mfastboot-v2>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2781 KB)...
OKAY [ 0.070s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing pmic ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing sdi ...
OKAY [ 1.442s]
finished. total time: 1.514s
c:\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (40960 KB)...
OKAY [ 0.930s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.579s
Click to expand...
Click to collapse
Try flashing the image again, it sometimes takes a few tries for it to flash. Also, I have gone between versions multiple times on my Moto X Force without issue. Just remember to NEVER do an OTA update or your device will be bricked.

DashBox said:
Try flashing the image again, it sometimes takes a few tries for it to flash. Also, I have gone between versions multiple times on my Moto X Force without issue. Just remember to NEVER do an OTA update or your device will be bricked.
Click to expand...
Click to collapse
I wanted to go down from 6.0.1 to 6.0 to be able to receive an OTA update to 7.0. Under which circumstances will OTA brick the device?

FredericDelany said:
I wanted to go down from 6.0.1 to 6.0 to be able to receive an OTA update to 7.0. Under which circumstances will OTA brick the device?
Click to expand...
Click to collapse
I think that should be fine as long as you go directly to 7.0 from 6.0. If you ever go back to lolipop, doing an OTA update to Android 6.0 would cause a brick as your bootloader has been updated to nougat and an OTA tries to downgrade the partitions which is what causes the brick.
So from what I know right now this is what will happen:
You downgrade to 6.0 then go directly 7.0 via OTA = device partitions and bootloader is updated to nougat. Device works fine
7.0 to 5.1.1 via Fastboot = Device works fine no issue. Just don't flash gpt.bin
5.1.1 to 6.0 or 6.0.1 via OTA = Brick as the 7.0 update updated the device's partitions.
5.1.1 to 6.0 or 6.0.1 via Fastboot = Device works fine. Just don't flash gpt.bin
If you ever downgrade and choose to upgrade again it is best to use fastboot to avoid a brick.
There is also no blankflash files to recover your device yet if you were to brick it so you need to remember that.
I bricked my Moto G2 by upgrading to Marshmallow, downgrading to KitKat and then running a 5.0.2 OTA update.

DashBox said:
I think that should be fine as long as you go directly to 7.0 from 6.0. If you ever go back to lolipop, doing an OTA update to Android 6.0 would cause a brick as your bootloader has been updated to nougat and an OTA tries to downgrade the partitions which is what causes the brick.
So from what I know right now this is what will happen:
You downgrade to 6.0 then go directly 7.0 via OTA = device partitions and bootloader is updated to nougat. Device works fine
7.0 to 5.1.1 via Fastboot = Device works fine no issue. Just don't flash gpt.bin
5.1.1 to 6.0 or 6.0.1 via OTA = Brick as the 7.0 update updated the device's partitions.
5.1.1 to 6.0 or 6.0.1 via Fastboot = Device works fine. Just don't flash gpt.bin
If you ever downgrade and choose to upgrade again it is best to use fastboot to avoid a brick.
There is also no blankflash files to recover your device yet if you were to brick it so you need to remember that.
I bricked my Moto G2 by upgrading to Marshmallow, downgrading to KitKat and then running a 5.0.2 OTA update.
Click to expand...
Click to collapse
I will now downgrade to 6.0.
Afterwards, may it brick my device, if they try to deliver OTA 6.0 security updates first, before updating to 7.0?

FredericDelany said:
I will now downgrade to 6.0.
Afterwards, may it brick my device, if they try to deliver OTA 6.0 security updates first, before updating to 7.0?
Click to expand...
Click to collapse
Not sure about security updates, if you can avoid them, avoid them. If not I think that could be fine. Not sure though.

DashBox said:
Not sure about security updates, if you can avoid them, avoid them. If not I think that could be fine. Not sure though.
Click to expand...
Click to collapse
I just tried it out, there was no possibility to avoid the security updates. Either way, they caused no problems.

How to downgrade moto g4 plus

i want to downgrade Moto g4 plus Indian version Marshmallow MPJ24.139-63 to Marshmallow MPJ24.139-13.1 if i downgrade i get issue wifi not connecting and baseband showing blank i have unlocked my bootloader

You have to flash the stock MM ROM, but skip flashing the bootloader.img, that's because you can't downgrade bootloader.

KiiKeEp said:
You have to flash the stock MM ROM, but skip flashing the bootloader.img, that's because you can't downgrade bootloader.
Click to expand...
Click to collapse
With fastboot? There is no problem doing that? :I

I flashed old rom bt its show gpt file something corupt and boot file and recoveryso i should skip this all files

im getting all this error C:\Users\SUNNY\Downloads\XT1641-XT1643_ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy
-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
C:\Users\SUNNY\Downloads\XT1641-XT1643_ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy
-DEFAULT_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.602s]
writing 'boot'...
(bootloader) Image not signed or corrupt
and for recovery also same

@sjadhav252 MPJ24.139-13.1 is not for INDIAN variants Download MPJ24.139-23.1 ...
And while flashing skip GPT and Bootloader both...

from where to download

if i flash MPJ24.139-23.1 this after that i update my phone via ota it will become official or not and why i see on bootloader logo console null-null is there any issue with that

sjadhav252 said:
from where to download
Click to expand...
Click to collapse
Check here, https://forum.xda-developers.com/moto-g4-plus/how-to/index-moto-g4-plus-factory-firmware-t3409033
After flashing this, you will receive update to 139-63 and then you will get update to nougat...
sjadhav252 said:
if i flash MPJ24.139-23.1 this after that i update my phone via ota it will become official or not and why i see on bootloader logo console null-null is there any issue with that
Click to expand...
Click to collapse
1st OTA to 139-63 will make it official again...
And i don't know what about null-null you said...

In this you can see console null-null im talking about that

That console NULL message is present in my (unlocked) bootloader too, I'm not sure what causes it or represents. I've not experienced any side effects from it however. Might disappear when you flash the ROM suggested by Madddy or might not.
Maybe others can confirm, from the looks of your posting you've got bigger issues to fix!

[Q] How to find correct stock rom for my model?

I'm sorry of this is a noob question, but I found this: http: // www . filefactory . com/folder/c6cdedc45a775d27 <--- which contained a bunch of stock roms. (I'm a new user, so I can't post links; just remove the spaces)
I bricked my phone with an incompatible SuperSU (stuck on Moto boot screen), so I need to flash 6.0.1 for XT1644 (I think it's unlocked/USA variant but idk)
I tried one that I found called "XT1625-XT1644_ATHENE-RETUS_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml_2.zip" which said that it was 6.0.1, but when I tried to flash, it said:
Code:
C:\Users\Mateo\Downloads\Extracted ROM>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.044s
Apparently, I'm flashing the wrong version of the firmware, but there's like 10 pages of downloads on the filefactory link, and it takes about an hour to download each... Can anyone help me out here?
Thanks!

That firmware should be okay, however that error is normal if you're attempting to flash a build older than the build you currently have/had. I'm guessing you had either MPJ24.139-64 or Nougat on your device before? Your updated bootloader and gpt blocks any downgrades (and thus reduces the chances of bricking your device).
You may be able to flash your older firmware (and downgrading in the process) if you do not flash gpt or bootloader, omit:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
The rest of your flashing commands should be the same. Of course, verify your bootloader is unlocked (which it should be if you were flashing SuperSU), else you won't be able to downgrade.

Thanks for your quick response!! I downgraded without problem! Also rooted with a compatible SuperSU this time... Then disabled the OTA daemon, so it wouldn't​ auto update, and brick myself, since I'm running an earlier version of the bootloader (correct me if I'm wrong...) Thanks again! :good:

matetoes said:
Thanks for your quick response!! I downgraded without problem! Also rooted with a compatible SuperSU this time... Then disabled the OTA daemon, so it wouldn't​ auto update, and brick myself, since I'm running an earlier version of the bootloader (correct me if I'm wrong...) Thanks again! :good:
Click to expand...
Click to collapse
Woo, good to hear you've got your device working I think with the OTA, you should be okay as the bootloader blocked earlier attempts to downgrade and your subsequent flashes won't have affected those partitions, so it's unlikely you'll brick your device!

Phone is dead

Hey!
My Moto g5 plus is dead and not even starting....only led is blinking near speaker.
Help me to resolve this issue.

What happened to your device before this? Did you take an OTA update, or flash something?

Try connecting it to a computer.

The blinking led refers to low battery, so maybe your charging circuit got fried and the charger is unable to charge your phone if its in warranty, visit moto service center or any local shop.

echo92 said:
What happened to your device before this? Did you take an OTA update, or flash something?
Click to expand...
Click to collapse
i just unlock boot loader and flash ota update and it stucks. please help

Yeah same here
Niel_ujle said:
Hey!
My Moto g5 plus is dead and not even starting....only led is blinking near speaker.
Help me to resolve this issue.
Click to expand...
Click to collapse
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
---------- Post added at 02:13 PM ---------- Previous post was at 02:10 PM ----------
DEV JC said:
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
Click to expand...
Click to collapse
any one help....
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
DEV JC said:
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
Click to expand...
Click to collapse
any one help....
---------- Post added at 02:14 PM ---------- Previous post was at 02:14 PM ----------
DEV JC said:
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
Click to expand...
Click to collapse
any one help....
---------- Post added at 02:32 PM ---------- Previous post was at 02:14 PM ----------
jaysamani said:
i just unlock boot loader and flash OTA update and it stucks. please help
Click to expand...
Click to collapse
I also tried the same
unlocked the bootloader and after I flashed stock ROM and then updated through OTA
now the device is not responding

DEV JC said:
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
---------- Post added at 02:13 PM ---------- Previous post was at 02:10 PM ----------
any one help....
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
any one help....
---------- Post added at 02:14 PM ---------- Previous post was at 02:14 PM ----------
any one help....
---------- Post added at 02:32 PM ---------- Previous post was at 02:14 PM ----------
I also tried the same
unlocked the bootloader and after I flashed stock ROM and then updated through OTA
now the device is not responding
Click to expand...
Click to collapse
These forums are not real time, so please be patient for a reply.
1)Which stock firmware did you have before unlocking your bootloader?
2)Which firmware did you flash and can you remember what the OTA was that you installed?

echo92 said:
These forums are not real time, so please be patient for a reply.
1)Which stock firmware did you have before unlocking your bootloader?
2)Which firmware did you flash and can you remember what the OTA was that you installed?
Click to expand...
Click to collapse
i do not remember which firmware i had before
but i installed the "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEF" firmware,
after that i got a ota update after installing the phone was dead...

DEV JC said:
i do not remember which firmware i had before
but i installed the "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEF" firmware,
after that i got a ota update after installing the phone was dead...
Click to expand...
Click to collapse
Ah, from the sounds of it you downgraded your stock firmware and then attempted to take an OTA update. You've likely corrupted your bootloader and thus hard bricked your device. This is why downgrading stock firmware is a bad idea...
All I can suggest is to try to use the albus (Moto Z2 Play) blankflash and Moto Z Play GPT/bootloader from this post https://forum.xda-developers.com/showpost.php?p=73062532&postcount=15 and use a TWRP flashable of a stock ROM. I do not know, and suspect you cannot, flash stock G5+ ROMs onto your device (possibly due to having a Moto Z Play bootloader), so hopefully there's a TWRP flashable of the Oreo stock ROM when that arrives.
If that blankflash does not work, then you may have to wait for a newer blankflash to be leaked (Motorola does not release these blankflash files, they are leaked, sometimes alongside firmware), perhaps when the Oreo factory image is leaked. We generally cannot build them from scratch as they require cryptographic signing by Motorola. The only other alternative is to send the device to a service centre and an expensive motherboard replacement.

Thanks
echo92 said:
Ah, from the sounds of it you downgraded your stock firmware and then attempted to take an OTA update. You've likely corrupted your bootloader and thus hard bricked your device. This is why downgrading stock firmware is a bad idea...
All I can suggest is to try to use the albus (Moto Z2 Play) blankflash and Moto Z Play GPT/bootloader from this post https://forum.xda-developers.com/showpost.php?p=73062532&postcount=15 and use a TWRP flashable of a stock ROM. I do not know, and suspect you cannot, flash stock G5+ ROMs onto your device (possibly due to having a Moto Z Play bootloader), so hopefully there's a TWRP flashable of the Oreo stock ROM when that arrives.
If that blankflash does not work, then you may have to wait for a newer blankflash to be leaked (Motorola does not release these blankflash files, they are leaked, sometimes alongside firmware), perhaps when the Oreo factory image is leaked. We generally cannot build them from scratch as they require cryptographic signing by Motorola. The only other alternative is to send the device to a service centre and an expensive motherboard replacement.
Click to expand...
Click to collapse
Thanks buddy for the solution...
it works man....
i need some more help....
where can i find the latest firmware...
my model is "XT1686" moto g5 plus

Hey...
I just recovered the dead Moto g5 plus...
Now I'm on pixel experience 8.1 ROM
I live in India....
I have a Jio 4G sim...
Which works perfectly but..Volte is not working....
I tried Aex 5.1 Volte issue is still there....
Any help pls....

DEV JC said:
Thanks buddy for the solution...
it works man....
i need some more help....
where can i find the latest firmware...
my model is "XT1686" moto g5 plus
Click to expand...
Click to collapse
did your phone start working? my one is not starting it stuck in bootloop i think.please answer asap

After that I flashed pixel experience ROM....
It works for me...
But LTE is now working.....
I think I should go for the service centre

echo92 said:
These forums are not real time, so please be patient for a reply.
1)Which stock firmware did you have before unlocking your bootloader?
2)Which firmware did you flash and can you remember what the OTA was that you installed?
Click to expand...
Click to collapse
i had latest Nov firmware before unlocking boot loader,
after that i flash "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" <-- this stock rom.
everything was good till i got ota update (which one i don't know but it was around 250 MB)
during this update phone died.
Now i am unable to boot my device in any mode
and i think i can flash "POTTER_NPN25.137-33_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" <-- this rom.
here is the output: :crying:
Microsoft Windows [Version 10.0.16299.192]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Users\jaysa\Desktop\motog5plus>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.126s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.453s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2164 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.090s]
finished. total time: 0.174s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.402s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.327s]
finished. total time: 0.740s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.495s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.443s]
finished. total time: 0.945s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.361s]
writing 'dsp'...
OKAY [ 0.200s]
finished. total time: 0.570s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (75642 KB)...
OKAY [ 1.671s]
writing 'oem'...
OKAY [ 0.653s]
finished. total time: 2.333s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (517327 KB)...
OKAY [ 11.275s]
writing 'system'...
OKAY [ 4.289s]
finished. total time: 15.589s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (502109 KB)...
OKAY [ 11.001s]
writing 'system'...
OKAY [ 4.078s]
finished. total time: 15.087s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (522558 KB)...
OKAY [ 11.413s]
writing 'system'...
OKAY [ 4.002s]
finished. total time: 15.423s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (500901 KB)...
OKAY [ 10.948s]
writing 'system'...
OKAY [ 3.933s]
finished. total time: 14.888s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (432777 KB)...
OKAY [ 9.473s]
writing 'system'...
OKAY [ 3.512s]
finished. total time: 12.996s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.5
error: cannot load 'system.img_sparsechunk.5'
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.6
error: cannot load 'system.img_sparsechunk.6'
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.7
error: cannot load 'system.img_sparsechunk.7'
C:\Users\jaysa\Desktop\motog5plus>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (74872 KB)...
OKAY [ 1.661s]
writing 'modem'...
OKAY [ 0.696s]
finished. total time: 2.366s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.038s]
finished. total time: 0.041s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.025s]
finished. total time: 0.027s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (2528 KB)...
OKAY [ 0.076s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.178s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase cache
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.032s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.075s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.025s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.036s
C:\Users\jaysa\Desktop\motog5plus>fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.022s]
finished. total time: 0.023s
C:\Users\jaysa\Desktop\motog5plus>fastboot reboot
rebooting...
finished. total time: 0.007s
C:\Users\jaysa\Desktop\motog5plus>
any help? what the **** is going with me?

jaysamani said:
i had latest Nov firmware before unlocking boot loader,
after that i flash "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" <-- this stock rom.
everything was good till i got ota update (which one i don't know but it was around 250 MB)
during this update phone died.
Now i am unable to boot my device in any mode
and i think i can flash "POTTER_NPN25.137-33_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" <-- this rom.
here is the output: :crying:
<snip>
any help? what the **** is going with me?
Click to expand...
Click to collapse
1)So you had the latest NPN25.137-92 firmware (November 2017) for XT1686 devices?
I'm not sure why you downgraded to the Jan 2017 NPN25.137-15 firmware (though it's deployed to Indian devices, the firmware is very old compared to what you had). By doing so, you set your device up for a hard brick - you effectively had a Nov 2017 bootloader, but a Jan 2017 system. As you cannot downgrade bootloaders, taking an OTA would likely have corrupted your bootloader and thus caused your device to hard brick.
2)I'm not sure which blankflash you used to rescue your device, hopefully it's the right one for G5 Plus devices (I asked you in the other thread you posted in).
I did say in the other thread as well that you will likely want to flash the NPN25.137-92 firmware using the procedure outlined in that guide, I do not understand why you're trying to flash the European/US NPN25.137-33 firmware, which might damage your device further. The pre-flash validation errors are from attempting to flash a stock ROM older than what was on your device (which would have been the November firmware, so thus you need to flash the Nov 2017 firmware). I understand you're desperate to get your device running again, please take a moment to properly read up on which firmware you need.
If the firmware flashes don't work, you may either have to wait for someone else to suggest other tips or submit your device for an expensive motherboard repair, and use this as a lesson to be careful if you downgrade.

jaysamani said:
i had latest Nov firmware before unlocking boot loader,
after that i flash "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" <-- this stock rom.
everything was good till i got ota update (which one i don't know but it was around 250 MB)
during this update phone died.
Now i am unable to boot my device in any mode
and i think i can flash "POTTER_NPN25.137-33_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" <-- this rom.
any help? what the **** is going with me?
Click to expand...
Click to collapse
You shouldn't have downgraded the bootloader, that causes an instant hard brick. Now that you've downgraded and got a hard brick, I'd suggest you wait for an update and use that full fastboot update to get it fixed or use the blankflash for 139-92 (if exists). Although I saw someone running 137-93 which could be a county-specific update or just some minor update as the guy just had his motherboard repaired and was running 137-93 instead of the 137-92 update which I believe everyone else is on or about to get.
Always remember not to downgrade Moto device's gpt and bootloader. And only take OTAs when you're either completely stock (locked bootloader with no system modifications) or unlocked bootloader with no system modifications.
Fellow members, please correct me if I missed something and do recommend suggestions.

psychopac said:
You shouldn't have downgraded the bootloader, that causes an instant hard brick. Now that you've downgraded and got a hard brick, I'd suggest you wait for an update and use that full fastboot update to get it fixed or use the blankflash for 139-92 (if exists). Although I saw someone running 137-93 which could be a county-specific update or just some minor update as the guy just had his motherboard repaired and was running 137-93 instead of the 137-92 update which I believe everyone else is on or about to get.
Always remember not to downgrade Moto device's gpt and bootloader. And only take OTAs when you're either completely stock (locked bootloader with no system modifications) or unlocked bootloader with no system modifications.
Fellow members, please correct me if I missed something and do recommend suggestions.
Click to expand...
Click to collapse
Just a couple of things to add on
1)It's not usually the act of downgrading which causes the hard brick, which appears to deceive users into believing it's okay to downgrade. As far as I know, it's installing an OTA whilst downgraded which causes the issue of a hard brick.
With bootloaders (at least on the G4 Plus, and I have no reason to think the G5 Plus is different in this regard), you cannot downgrade a bootloader, it'll block you with a security downgrade error. However, you could still downgrade your firmware. In this case, the user still had the Nov 2017 bootloader but likely the Jan 2017 system. In taking an OTA, the OTA update appears to have no checks regarding the bootloader - it appears to assume that your bootloader is the same patch level as your system (i.e. in this case it'd assume you'd have the Jan 2017 bootloader too). Normally, with a locked bootloader or a device with the same firmware patch level, this would apply. With a downgrade, that's an incorrect and dangerous assumption, with the OTA seemingly having authorisation to overwrite the newer bootloader and causing a hard brick with a corrupted bootloader (corrupting the newer Nov 2017 bootloader, from what I understand).
Granted, Motorola's naming system for firmware builds is not very helpful, with different builds for different regions, though I imagine they'd argue that unlocking the bootloader means flashing the correct firmware and finding said firmware is now our responsibility.
2)I'm not sure if there is a NPN25.137-92 compatible blankflash (and I'm not sure if the albus blankflash still works), if not then we'd have to wait for a leaked blankflash from Motorola, either from a friendly contact within the engineering teams or a major OS update (e.g. the Oreo factory ROM). Somehow, the above user has managed to get back to fastboot despite appearing to hard brick their device... I've suggested to them to try flashing the NPN25.137-92 firmware if they are booting to fastboot reliably.
I do agree with the general message in your post though that downgrading is very risky and OTA updates should only be taken on particular firmware setups - namely, a device all on the same firmware patch level and no modifications, and not on the mixed firmware level that a downgrade would cause. Having a £200+ (or your regional equivalent) fancy paperweight is not fun to see...

echo92 said:
Just a couple of things to add on
1)It's not usually the act of downgrading which causes the hard brick, which appears to deceive users into believing it's okay to downgrade. As far as I know, it's installing an OTA whilst downgraded which causes the issue of a hard brick.
With bootloaders (at least on the G4 Plus, and I have no reason to think the G5 Plus), you cannot downgrade a bootloader, it'll block you with a security downgrade error. However, you could still downgrade your firmware. In this case, the user still had the Nov 2017 bootloader but likely the Jan 2017 system. In taking an OTA, the OTA update appears to have no checks regarding the bootloader - it appears to assume that your bootloader is the same patch level as your system (i.e. in this case it'd assume you'd have the Jan 2017 bootloader too). Normally, with a locked bootloader or a device with the same firmware patch level, this would apply. With a downgrade, that's an incorrect and dangerous assumption, with the OTA having authorisation to overwrite the newer bootloader and causing a hard brick with a corrupted bootloader (corrupting the newer Nov 2017 bootloader, from what I understand).
Granted, Motorola's naming system for firmware builds is not very helpful, with different builds for different regions, though I imagine they'd argue that unlocking the bootloader means flashing the correct firmware and finding said firmware is now our responsibility.
2)I'm not sure if there is a NPN25.137-92 compatible blankflash (and I'm not sure if the albus blankflash still works), if not then we'd have to wait for a leaked blankflash from Motorola, either from a friendly contact within the engineering teams or a major OS update (e.g. the Oreo factory ROM). Somehow, the above user has managed to get back to fastboot despite appearing to hard brick their device... I've suggested to them to try flashing the NPN25.137-92 firmware if they are booting to fastboot reliably.
I do agree with the general message in your post though that downgrading is very risky and OTA updates should only be taken on particular firmware setups - namely, a device all on the same firmware patch level and no modifications, and not on the mixed firmware level that a downgrade would cause. Having a £200+ (or your regional equivalent) fancy paperweight is not fun to see...
Click to expand...
Click to collapse
Good to know that he had access to fastboot. He now has a chance to flash the 137-92 in order to get his phone up and running. And thanks for the info.

Done But still one Issue!
echo92 said:
Just a couple of things to add on
1)It's not usually the act of downgrading which causes the hard brick, which appears to deceive users into believing it's okay to downgrade. As far as I know, it's installing an OTA whilst downgraded which causes the issue of a hard brick.
With bootloaders (at least on the G4 Plus, and I have no reason to think the G5 Plus is different in this regard), you cannot downgrade a bootloader, it'll block you with a security downgrade error. However, you could still downgrade your firmware. In this case, the user still had the Nov 2017 bootloader but likely the Jan 2017 system. In taking an OTA, the OTA update appears to have no checks regarding the bootloader - it appears to assume that your bootloader is the same patch level as your system (i.e. in this case it'd assume you'd have the Jan 2017 bootloader too). Normally, with a locked bootloader or a device with the same firmware patch level, this would apply. With a downgrade, that's an incorrect and dangerous assumption, with the OTA seemingly having authorisation to overwrite the newer bootloader and causing a hard brick with a corrupted bootloader (corrupting the newer Nov 2017 bootloader, from what I understand).
Granted, Motorola's naming system for firmware builds is not very helpful, with different builds for different regions, though I imagine they'd argue that unlocking the bootloader means flashing the correct firmware and finding said firmware is now our responsibility.
2)I'm not sure if there is a NPN25.137-92 compatible blankflash (and I'm not sure if the albus blankflash still works), if not then we'd have to wait for a leaked blankflash from Motorola, either from a friendly contact within the engineering teams or a major OS update (e.g. the Oreo factory ROM). Somehow, the above user has managed to get back to fastboot despite appearing to hard brick their device... I've suggested to them to try flashing the NPN25.137-92 firmware if they are booting to fastboot reliably.
I do agree with the general message in your post though that downgrading is very risky and OTA updates should only be taken on particular firmware setups - namely, a device all on the same firmware patch level and no modifications, and not on the mixed firmware level that a downgrade would cause. Having a £200+ (or your regional equivalent) fancy paperweight is not fun to see...
Click to expand...
Click to collapse
thank you all for all your support
just i flash "POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" ROM
and now it shows that oem_locked and software status is official
but still it is in boot loop(now it shows Motorola logo and it restarts)
Can i give it to service it is under warranty?
Once again thank you thank you
now at locked boot loader what can i do?

jaysamani said:
thank you all for all your support
just i flash "POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" ROM
and now it shows that oem_locked and software status is official
but still it is in boot loop(now it shows Motorola logo and it restarts)
Can i give it to service it is under warranty?
Once again thank you thank you
now at locked boot loader what can i do?
Click to expand...
Click to collapse
If you've got a locked bootloader, and it's bootlooping, there's not much we can do.
Did you fully wipe your device (wipe cache, and factory reset), to verify that there's nothing on your device that might be causing an issue?
It might be due to the blankflash you used, again, can you please show which blankflash you used to rescue your device?
Can you get us your getvar info to have a look please?
1)Boot your device to the bootloader. Connect your device to the computer.
2)In the ADB terminal, type 'fastboot getvar all' (without quotes) and press Enter.
3)Copy the output to a post here, you may wish to remove your IMEI. This output is a list of your device variables and should tell us if the firmware flashed okay.
Unfortunately, because your bootloader was unlocked, Motorola has a record of the unlock key being requested against your IMEI and thus your remaining Motorola warranty is void. Regardless of your device showing oem_locked and no bootloader unlocked warning, your IMEI would indicate that void warranty. There are instances where service centres have looked at the paperwork and simply repaired your device, however, I do not know if in this instance the service centre would do this. You may have to pay for an expensive motherboard replacement (about 70 % of the device cost, from what I understand). It's up to you if you want to get your device repaired or put the money towards a new device.
As an aside, this is one of the reasons why downgrading can be very risky...

Latest Firmware for XT 1686 Indian Variant.

Hi guys finally i managed to unbrick the hard bricked phone ...
now my question is how should i choose the stock firmware for my device which is Indian variant - XT1686 32 GB
Bcoz as there are lots of different variants .... i have tried brazil
XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2017-02-05
this doesnt give IMEI numbers it will make them 0 so can u guys please tell me how should i choose the variants

and also please if some one have the recent boot loader.img, recovery.img and gpt.bin please provide me im stuck in boot loop ... just the sake until we get oreo update - XT1686 is my phone
i am not able to use my phone right now request you guys....

It's normal not to have your IMEI on stock if you've flashed Oreo ROMs before.
You can follow instructions in this thread if you want to get IMEI back.
Happy flashing!

Jrhotrod said:
It's normal not to have your IMEI on stock if you've flashed Oreo ROMs before.
You can follow instructions in this thread if you want to get IMEI back.
Happy flashing!
Click to expand...
Click to collapse
now actually my phone is stuck with Moto Z2 play boot loader so that i need everything to be Moto z2 play's firmware .... to wake up the dead phone it took me around 4 hours .... So my boot loader is not letting me install any other firmwares on my phone
please help me :crying:
This is what i got when i tried to flash Moto g5 plus Boot loader by downloading all the firmwares from official website:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.118s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.405s

praveen Glaxi said:
now actually my phone is stuck with Moto Z2 play boot loader so that i need everything to be Moto z2 play's firmware .... to wake up the dead phone it took me around 4 hours .... So my boot loader is not letting me install any other firmwares on my phone
please help me :crying:
This is what i got when i tried to flash Moto g5 plus Boot loader by downloading all the firmwares from official website:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.118s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.405s
Click to expand...
Click to collapse
What on Earth did you do to get the Z2 bootloader and how did you get it to even flash in the first place?

Jrhotrod said:
What on Earth did you do to get the Z2 bootloader and how did you get it to even flash in the first place?
Click to expand...
Click to collapse
Okay dude .... Let me explain very quickly ....
First off I bought this device like 8 months ago .... 1 week b4 I flashed customs ROM that is lineago os 15.1 which was recent for my device .... Everything was fine until yrstdy.... Yrstdy morning what I did was I planned to flash normal stock ROM to my phone .... Using some brasil version by watching YouTube ... Everything went well I was like thank god and then I inserted the sim but there was not network due to imei issue ....
This is where problem started...
Thinking after I do the OTA update security patch might go back and I might get the signal but then I did ota update and phone restarted ... It showed installing updates in half wat it suddenly switched I realised that I hard bricked my phone ...
Then searched the whole xda forums and found this guide https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457/page6
By Rakesh1b.....
I did the same I used potter blank flash and my phone woke up after trying it several hours....
Then when I tried to flash bootloader of moto g5 plus it showed error like I previously displayed ..... Well there was one more post for all of these 3 files, bootloader.IMG gpt.bin and recovery.IMG well I did flash all of them they seem to be worked ...
Then I tried to flash moto g5 plus twrp recovery which gave me error of failure...
Then I tried moto z2 play twrp ... God damn it got flashed and went into twrp recovery then as I studied as per @Rakesh1b ......
And now I'm stuck here ..... Not able to go front...
I get error like /cache not found when I try to flash custom os ...
What all I need now is moto g5 plus boot loader.IMG recovery.IMG gpt.bin
Of January security patch ... Mine last update was November security patch
I request some one to give those files or give a proper solution for this plzzzzzz

praveen Glaxi said:
I did the same I used potter blank flash and my phone woke up after trying it several hours....
Then when I tried to flash bootloader of moto g5 plus it showed error like I previously displayed ..... Well there was one more post for all of these 3 files, bootloader.IMG gpt.bin and recovery.IMG well I did flash all of them they seem to be worked ...
Then I tried to flash moto g5 plus twrp recovery which gave me error of failure...
Then I tried moto z2 play twrp ... God damn it got flashed and went into twrp recovery then as I studied as per @Rakesh1b ......
And now I'm stuck here ..... Not able to go front...
I get error like /cache not found when I try to flash custom os ...
What all I need now is moto g5 plus boot loader.IMG recovery.IMG gpt.bin
Of January security patch ... Mine last update was November security patch
I request some one to give those files or give a proper solution for this plzzzzzz
Click to expand...
Click to collapse
Thank you for the explanation, your situation seems to (mostly) make sense to me now.
You probably realize this in retrospect, but you should not have accepted an OTA on stock with no IMEI. But enough with that, what exactly do you mean by "my phone woke up"? I'd love to offer you a solution, but to find one, I'll need to know if "waking up" involved booting into Android, booting into the bootloader, or whatever.

u should unlock bootloader first.. the version of bootloader is lower than on ur phone, you should not OTA update, OTA did upgraded ur bootloader ver to latest..
---------- Post added at 06:32 AM ---------- Previous post was at 06:28 AM ----------
Try this firmware for ur model latest from february 2018
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
or
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
---------- Post added at 06:54 AM ---------- Previous post was at 06:32 AM ----------
[/COLOR]if u followed this solution and unbricked ur devices,try this Rom
its debloated and deodexed stock rom
: https://doc-00-6o-docs.googleuserco...2322377&hash=4s4e5hh6kltpi7nthp0actt4434mbjof
Orginal post :
https://forum.xda-developers.com/g5-plus/development/stock-debloated-deodexed-t3619972
THE FIRST THING U SHOULD TO UNLOCK BOOTLOADER before to try and CWM OR TWRP, custom rom..

Hey guys thanks for everyone's assistance here
i have successfully flashed Pixel experience ROM to my phone by using this procedure
1st. Blank flash your phone as per the above procedure..... (disable signature enforcement if u are using windows 10)
press and hold power button you could hear that mobile disconnects and connects once you hear that then press voldown and power with one hand and run blankflash.bat and then release those buttons before u hear them again
2nd. Flash all 3 provided files in MotoG5Plus_addison2Potter in the attachement and it will take you to the boot loader
Using these Commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Fastboot flash recovery recovery.img
fastboot reboot-bootloader
(Flash the files from provided Zip attachment)
3rd. download Moto z2 play or plus twrp recovery as i didnt have time to compress everything i cud nt provide that, then flash the custom recovery, then try to enter into recovery mod and it should enter..... if u have done 1st and 2nd step properly then u will enter into TWRP recvery mod
and here is the link for debolated ROM download version 2 which has november patch on it....
https://forum.xda-developers.com/g5-...dexed-t3619972
then once ur in twrp mount it to ur pc and copy the debolate ROM to ur phone and then flash it though TWRP ....
once it is done reboot ur phone into os and it should successfully boot into ROM...
once done u can flash any custom ROM into ur phone using TWRP
But 1 major issue is that i lost 4g or VoLTE:
Can u guys please help me with that.....