Database Users

Flashing back to Stock, Trying to understand Errors

So I ran into some issues installing LOS15 and flashed back to stock using POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
Being paranoid I am concerned about the errors I have gotten, mainly because if the ROM messed with my system and I cannot replace it, well, who know what nefarious actions might be taking place.
I have booted the system and it works fine, but again, just being cautious.
Here are the errors:
Code:
[B]fastboot flash partition gpt.bin[/B]
sending 'partition' (45 KB)...
OKAY [ 0.005s]
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.074s
[B]fastboot flash bootloader bootloader.img[/B]
sending 'bootloader' (5115 KB)...
OKAY [ 0.233s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.510s
[B]sudo fastboot flash boot boot.img [/B]
ending 'boot' (16384 KB)...
OKAY [ 0.771s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.442s]
finished. total time: 1.213s
[B]sudo fastboot flash recovery recovery.img [/B]
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.973s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.532s]
[B]
sudo fastboot erase customize[/B]
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
[B]sudo fastboot erase clogo [/B]
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s

Is your moto g5 plus reteu?

InsaneNexuS said:
Is your moto g5 plus reteu?
Click to expand...
Click to collapse
I guess you meant retail? Yeah, it is retail. No amazon ads.

Well I need to know if it was reteu software channel. Otherwise it wont work for you. Maybe because your not flashing the right files? Mine was RETEU, which means its a european model.

No, not European. US Version. At least I bought it on Amazon in the US.
I want to add that I have flashed the stock before and did not get these errors. It only happened after I flashed LOS15.

Well then you need to find the right firmware for you US model. And start with locking the bootloader. And flash every line one by one (copy paste). Dont copy all of them and paste them otherwise it wont work. You really have to do it one by one.
Bootloader relock commands:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
After you locked the bootloader start flashing the firmware. Use this site to find the right firmware:https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I gues you should try the one that says RETAIL in the name.
---------- Post added at 23:01 ---------- Previous post was at 22:59 ----------
NODE06 said:
No, not European. US Version. At least I bought it on Amazon in the US.
I want to add that I have flashed the stock before and did not get these errors. It only happened after I flashed LOS15.
Click to expand...
Click to collapse
Well if you have done it before then I guess I don't really know what the problem is

Here's what happened putting in that code:
Code:
sudo fastboot oem lock
[sudo] password for user:
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.002s]
finished. total time: 0.002s
sudo fastboot oem lock
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.012s]
finished. total time: 0.012s
sudo fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (75638 KB)...
OKAY [ 3.432s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.499s
I guess I would just like to know why this is happening. like what does "(bootloader) Security version downgrade" even mean?

Your are downgrading, trying to flash a version of firmware that is older than what is installed already.
You either need a newer factory image, or are using the incorrect one. "Preflash validation failed" is basically saying the digitial signature doesn't match what is already there or is older than what you have currently.
Exactly what image are you flashing and what is the output of "fastboot getvar all" except mask out the IMEI number(s).

acejavelin said:
Your are downgrading, trying to flash a version of firmware that is older than what is installed already.
You either need a newer factory image, or are using the incorrect one. "Preflash validation failed" is basically saying the digitial signature doesn't match what is already there or is older than what you have currently.
Exactly what image are you flashing and what is the output of "fastboot getvar all" except mask out the IMEI number(s).
Click to expand...
Click to collapse
Yeah, I thought that was the issue. I guess I just kind of fracked my phone then because I installed Lineage 15.0 which uses Android O. I guess there will not be a newer firmware image anytime soon.
The flash back to stock works but I would rather have everything original. This code is with Resurrection ROM. Will be glad if you can explain any of it!
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224538B8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8a
(bootloader) uid: 7C6B3F8100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-18-2017
(bootloader) sku: XT1687
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:41:43 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:7.0/NPN25.1
(bootloader) ro.build.fingerprint[1]: 37-35/37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.37.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.08R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g6508460 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Feb 14 06:47:06 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.026s

NODE06 said:
Yeah, I thought that was the issue. I guess I just kind of fracked my phone then because I installed Lineage 15.0 which uses Android O. I guess there will not be a newer firmware image anytime soon.
The flash back to stock works but I would rather have everything original. This code is with Resurrection ROM. Will be glad if you can explain any of it!
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224538B8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8a
(bootloader) uid: 7C6B3F8100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-18-2017
(bootloader) sku: XT1687
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:41:43 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:7.0/NPN25.1
(bootloader) ro.build.fingerprint[1]: 37-35/37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.37.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.08R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g6508460 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Feb 14 06:47:06 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.026s
Click to expand...
Click to collapse
No, you don't understand... Your "firmware" in this case means bootloader/partition table/radios, it has nothing to do with any custom ROM you would flash, but the last stock firmware you had installed, which in your case was NPN25.137-35 (Blur_Version.25.11.37.potter.retail.en.US) and a radio of M8953_02.03.07.08R POTTER_NA_CUST, so you need that version or higher.
Which seems odd, because that is newer than my version which is completely stock and untouched.... NPNS25.137-33-5/M8953_02.03.07.06R... So I am assuming you were on a special Verizon test build? You will need one of those except the same version or newer than when you were last stock.

acejavelin said:
No, you don't understand... Your "firmware" in this case means bootloader/partition table/radios, it has nothing to do with any custom ROM you would flash, but the last stock firmware you had installed, which in your case was NPN25.137-35 (Blur_Version.25.11.37.potter.retail.en.US) and a radio of M8953_02.03.07.08R POTTER_NA_CUST, so you need that version or higher.
Which seems odd, because that is newer than my version which is completely stock and untouched.... NPNS25.137-33-5/M8953_02.03.07.06R... So I am assuming you were on a special Verizon test build? You will need one of those except the same version or newer than when you were last stock.
Click to expand...
Click to collapse
I use Consumer Cellular, and the only thing I did that started screwing everything up was install Lineage 15 which is based on Android Oreo. Could that have change it to the newer version?

NODE06 said:
I use Consumer Cellular, and the only thing I did that started screwing everything up was install Lineage 15 which is based on Android Oreo. Could that have change it to the newer version?
Click to expand...
Click to collapse
I don't know about Consumer Cellular but I think they are an AT&T MVNO so it probably isn't relevant.
Any custom ROM you flashed is not relevant either... to go back to stock you must flash a same or newer firmware than what you have, and you are confusing what that means. Lineage, or any custom ROM, does not modify your firmware, only your system and boot partitions, your firmware is in the bootloader/radios and is related to your gpt.bin (the partition table). You need a factory image that is the same or newer than what you have, which I don't think is available since Moto isn't very forthcoming with factory images (and your version is very new, newer than mine), but this has nothing to do with flashing a custom ROM.
I haven't tried this on this device, but on older Moto devices you would downgrade by flashing the firmware but skipping gpt.bin and bootloader.img (you also cannot relock the booloader) and continuing with the other parts of the firmware image. Yes, the booloader and partition table no longer match the radios and rest of the ROM, but that usually fixes itself during the next major OTA update.

acejavelin said:
I don't know about Consumer Cellular but I think they are an AT&T MVNO so it probably isn't relevant.
Any custom ROM you flashed is not relevant either... to go back to stock you must flash a same or newer firmware than what you have, and you are confusing what that means. Lineage, or any custom ROM, does not modify your firmware, only your system and boot partitions, your firmware is in the bootloader/radios and is related to your gpt.bin (the partition table). You need a factory image that is the same or newer than what you have, which I don't think is available since Moto isn't very forthcoming with factory images (and your version is very new, newer than mine), but this has nothing to do with flashing a custom ROM.
I haven't tried this on this device, but on older Moto devices you would downgrade by flashing the firmware but skipping gpt.bin and bootloader.img (you also cannot relock the booloader) and continuing with the other parts of the firmware image. Yes, the booloader and partition table no longer match the radios and rest of the ROM, but that usually fixes itself during the next major OTA update.
Click to expand...
Click to collapse
I understand what you are saying, but I am telling you I flashed the same stock firmware a month ago with no issues.
The only thing that changed everything was installing the Lineage ROM. Could the Linage ROM have messed up my partition tables? I was having issues when I tried to install it relating to data encryption. But I have no idea how I could have flashed a newer version of anything. This is why I am so confused.

NODE06 said:
I understand what you are saying, but I am telling you I flashed the same stock firmware a month ago with no issues.
The only thing that changed everything was installing the Lineage ROM. Could the Linage ROM have messed up my partition tables? I was having issues when I tried to install it relating to data encryption. But I have no idea how I could have flashed a newer version of anything. This is why I am so confused.
Click to expand...
Click to collapse
Eh, not mess up, but it could change the filesystem type for a partition or two, sometimes system or data. You could use TWRP and try a repair on them.
Can't you just restore a TWRP backup first, then flash stock?
Sorry, but I may be a considered a wizard by some with some Moto devices, but I am really new to this one and it seems to have a few different quirks. Hopefully someone else can jump in here.
Are you using an official image? They usually contain a file called flashfile.xml, that will tell you what commands you need to enter to flash and what version it is, the above instructions are to relock a stock device, not return to stock.

acejavelin said:
Eh, not mess up, but it could change the filesystem type for a partition or two, sometimes system or data. You could use TWRP and try a repair on them.
Can't you just restore a TWRP backup first, then flash stock?
Sorry, but I may be a considered a wizard by some with some Moto devices, but I am really new to this one and it seems to have a few different quirks. Hopefully someone else can jump in here.
Are you using an official image? They usually contain a file called flashfile.xml, that will tell you what commands you need to enter to flash and what version it is, the above instructions are to relock a stock device, not return to stock.
Click to expand...
Click to collapse
He's flashing a stock.zip I believe.

aaronrw said:
He's flashing a stock.zip I believe.
Click to expand...
Click to collapse
Not with fastboot...
@NODE06 What exactly are you flashing and how?

acejavelin said:
Not with fastboot...
@NODE06 What exactly are you flashing and how?
Click to expand...
Click to collapse
I am flashing
POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
on Linux using ADB, yes, fastboot. I have done it often enough on this phone and used to do it on my G4.
I am wondering, looking at the flashfile.xml, if I should flash them in the same order they are listed in that file. But again, it does not make sense since the only think I did was install Lineage 15 when I was running Resurrection. I will try again to repair with TWRP, maybe I am missing something.
I am back on Resurrection and things are running fine, but I am concerned now that Lineage 15 might be doing some really weird stuff.

I notice the flashfile.xml has
Code:
<sparsing enabled="true" max-sparse-size="536870912"/>
<step operation="getvar" var="max-sparse-size"/>
in it.
Do they matter at all?
When I run the fastboot command I get a different number
Code:
sudo fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.008s

So, I fixed it. And yeah, you need to fastboot stock in the same order as the flashfile.xml and include the getvar max-sparse-size. Here is what worked for me. I got no errors besides the "bad key" for boot and recovery images.
Code:
sudo fastboot getvar max-sparse-size
sudo fastboot oem fb_mode_set
sudo fastboot flash partition gpt.bin
sudo fastboot flash bootloader bootloader.img
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash oem oem.img
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase DDR
sudo fastboot oem fb_mode_clear
sudo fastboot reboot

Should I bother upgrading from MM?

I'm on Pure Nexus, and I'm contemplating whether or not to even bother with this NPH25.200-22 update.
I'm looking for a good, stable, custom ROM that's themeable.

abense said:
I'm on Pure Nexus, and I'm contemplating whether or not to even bother with this NPH25.200-22 update.
I'm looking for a good, stable, custom ROM that's themeable.
Click to expand...
Click to collapse
I'd go with aicp or dirty unicorns personally. I think these roms are definitely worth the upgrade and they're both extremely stable. AICP has a thread here on xda. Called the Android Ice Cold Project...and dirty unicorns has a website and g+ page.

Okay, I decided to do this:
Moto X Pure Factory Firmware Nougat NPH25.200-22
Here's my batch commands (I removed the line where it erase's user data)
Code:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
And then I downloaded the latest TWRP, 3.2.1.0
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.2.1-0-clark.img
fastboot reboot recovery
Performing a backup of everything onto my ext-sdcard.
Going with AICP, just like I did 2 years ago when I first got this thing.
installing this version: aicp_clark_n-12.1-NIGHTLY-20171213.zip
And open_gapps-arm64-7.1-nano-20171216.zip
Here goes...

SuperSU from here
http://www.supersu.com/download
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip

abense said:
SuperSU from here
http://www.supersu.com/download
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Click to expand...
Click to collapse
I'd go magisk, it's so simple to flash, and passes safety net easily, it's such a Breeze, and definitely the way to go rather than superSU!

So, it appears that I need to flash the MM radios?? I'm not getting LTE
Oh I already regret this.

abense said:
So, it appears that I need to flash the MM radios?? I'm not getting LTE
Oh I already regret this.
Click to expand...
Click to collapse
Probably best to flash the stock Nougat image via fastboot first, verify operation, then TWRP and root/ROM.

What's the part about bricking if I upgrade/downgrade modem firmware?

Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA394xxxxx
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 10-29-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 30 21:11:20 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:7.0/NPH
(bootloader) ro.build.fingerprint[1]: 25.200-22/21:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.22.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not available>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ge617f58 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Aug 29 00:53:54 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=2d08904-dirty
(bootloader) hyp.git: git=2d08904-dirty
(bootloader) sdi.git: git=d9f358f
(bootloader) pmic.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) aboot.git: git=MBM-NG-VA0.52-0-g69ca042
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (142)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.016s

abense said:
What's the part about bricking if I upgrade/downgrade modem firmware?
Click to expand...
Click to collapse
That's not the problem... the "bricking" issue is if you are on Nougat, then downgrade the ENTIRE device to Marshmallow, then take the Nougat OTA update again, this will cause a hard brick. Simply flashing the modems does not cause a problem with bricking.

acejavelin said:
Probably best to flash the stock Nougat image via fastboot first, verify operation, then TWRP and root/ROM.
Click to expand...
Click to collapse
acejavelin said:
That's not the problem... the "bricking" issue is if you are on Nougat, then downgrade the ENTIRE device to Marshmallow, then take the Nougat OTA update again, this will cause a hard brick. Simply flashing the modems does not cause a problem with bricking.
Click to expand...
Click to collapse
Gotcha.
Do you have any insight as to this problem? I ran a getvar all that you suggested in another thread.
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark

abense said:
Gotcha.
Do you have any insight as to this problem? I ran a getvar all that you suggested in another thread.
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark
Click to expand...
Click to collapse
Does it work properly stock, before doing anything?

Need to use this
https://forum.xda-developers.com/showpost.php?p=74999345&postcount=1061

What if...?
acejavelin said:
That's not the problem... the "bricking" issue is if you are on Nougat, then downgrade the ENTIRE device to Marshmallow, then take the Nougat OTA update again, this will cause a hard brick. Simply flashing the modems does not cause a problem with bricking.
Click to expand...
Click to collapse
What if I were to manually downgrade to stock Marshmallow and then install the factory image for 7.0 later on?

Bill720 said:
What if I were to manually downgrade to stock Marshmallow and then install the factory image for 7.0 later on?
Click to expand...
Click to collapse
As was said, it involves taking an OTA upgrade, not using a factory image... You're good there.

No OTA updates and no support? Am I on stock ROM or .......???

My first G5 Plus was stolen June last year (2018). Because it was uncertain if the insurance would pay and the G5 Plus was replaced by the bigger G5S Plus at that time, I decided to buy a second hand G5 Plus.
I didn’t knew than what I do know now. Anyway, things looked good, latest security update (June 2018)
I knew the Oreo update was coming, so I didn’t wonder I didn’t get a security update. But in November I saw Oreo was released in my country (the Netherlands), so I started worrying. I didn’t receive one on OTA reteu channel.
Some three weeks ago I contacted Motorola support and they told me they couldn’t help me because the warranty was void. So I started reading on XDA.
I want to stay on stock ROM for now, until Motorola stops security updates, so probably mid this year?
I wanted to flash fastboot to Oreo, but then I read about 0 IMEI, problems with persist etc.
I tried the Lenovo Motorola Smart Assistant but that one says unsupported device.
I don’t want to brick my phone and I don’t know the status or how to update my phone to stock Oreo and be able to receive OTA updates. From what I know and can see the bootloader is locked, but I don’t know what happened to the phone when it was rooted, flashed, which version etc.
Can you please help me? It’s really appreciated.
Here’s my ADB output:
C:\DATA\G5Plus\Minimal ADB and Fastboot>fastboot devices
XXXXXXX fastboot
C:\DATA\G5Plus\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8C
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: XXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 3B7E68F800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: IMEI number present XXXXXXXX
(bootloader) meid:
(bootloader) date: 07-06-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jun 25 21:41:19 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-92-14/16:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.331.16.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47e POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gf055b2e-0010
(bootloader) kernel.version[1]: 7-g516eb24 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed May 30 15:51:32 CDT 20
(bootloader) kernel.version[4]: 18
(bootloader) sbl1.git: git=MBM-NG-VC0.8C-0-g22013cf
(bootloader) rpm.git: git=202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8C-0-gcba6d5d
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.437s
C:\DATA\G5Plus\Minimal ADB and Fastboot>

Confused74 said:
My first G5 Plus was stolen June last year (2018). Because it was uncertain if the insurance would pay and the G5 Plus was replaced by the bigger G5S Plus at that time, I decided to buy a second hand G5 Plus.
I didn’t knew than what I do know now. Anyway, things looked good, latest security update (June 2018)
I knew the Oreo update was coming, so I didn’t wonder I didn’t get a security update. But in November I saw Oreo was released in my country (the Netherlands), so I started worrying. I didn’t receive one on OTA reteu channel.
Some three weeks ago I contacted Motorola support and they told me they couldn’t help me because the warranty was void. So I started reading on XDA.
I want to stay on stock ROM for now, until Motorola stops security updates, so probably mid this year?
I wanted to flash fastboot to Oreo, but then I read about 0 IMEI, problems with persist etc.
I tried the Lenovo Motorola Smart Assistant but that one says unsupported device.
I don’t want to brick my phone and I don’t know the status or how to update my phone to stock Oreo and be able to receive OTA updates. From what I know and can see the bootloader is locked, but I don’t know what happened to the phone when it was rooted, flashed, which version etc.
Can you please help me? It’s really appreciated.
Here’s my ADB output:
C:\DATA\G5Plus\Minimal ADB and Fastboot>fastboot devices
XXXXXXX fastboot
C:\DATA\G5Plus\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8C
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: XXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 3B7E68F800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: IMEI number present XXXXXXXX
(bootloader) meid:
(bootloader) date: 07-06-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jun 25 21:41:19 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-92-14/16:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.331.16.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47e POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gf055b2e-0010
(bootloader) kernel.version[1]: 7-g516eb24 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed May 30 15:51:32 CDT 20
(bootloader) kernel.version[4]: 18
(bootloader) sbl1.git: git=MBM-NG-VC0.8C-0-g22013cf
(bootloader) rpm.git: git=202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8C-0-gcba6d5d
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.437s
C:\DATA\G5Plus\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You can update Oreo by fastboot, and you don't lose any IMEI or persist as your just upgrading it and you won't brick your device also.as you are upgrading, not degrading. So you won't brick your device.

riyan65 said:
You can update Oreo by fastboot, and you don't lose any IMEI or persist as your just upgrading it and you won't brick your device also.as you are upgrading, not degrading. So you won't brick your device.
Click to expand...
Click to collapse
Thank you for your quick reply.
Nice to hear that it's safe to update to stock Oreo. From what I read there's no difference anymore in stock rom for different channels and models, it this true?
So I can use any fastboot stock Oreo rom vor my XT1685 on RETEU channel?
So f.i. : POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And if so, is the procedure below the proper one to flash using fastboot?
- Download adb fastboot tool and extract it on C:/ drive
- Now extract the downloaded ROM file to the adb fastboot folder.
- Once you are finished, open the command window by holding the SHIFT KEY and Right Mouse click.
- Now you need to sideload the OTA Oreo file to your phone. To do that, execute the following commands
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata[/I]
- Wait for a couple of minutes, once it is done. Now reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
- Once the installation is completed, enjoy the Oreo build OPS28.85-17 on your phone.
Or should I do the relatively easy OTA update described in here: https://forum.xda-developers.com/g5-plus/how-to/download-official-moto-g5-g5-plus-t3848246
since I seem to be running Indian firmware (92 instead of the 93 which I should be running for Europe).
Or is this way riskier with loss of IMEI etc. ?
Thanks in advance for your answer.

Confused74 said:
Thank you for your quick reply.
Nice to hear that it's safe to update to stock Oreo. From what I read there's no difference anymore in stock rom for different channels and models, it this true?
So I can use any fastboot stock Oreo rom vor my XT1685 on RETEU channel?
So f.i. : POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And if so, is the procedure below the proper one to flash using fastboot?
- Download adb fastboot tool and extract it on C:/ drive
- Now extract the downloaded ROM file to the adb fastboot folder.
- Once you are finished, open the command window by holding the SHIFT KEY and Right Mouse click.
- Now you need to sideload the OTA Oreo file to your phone. To do that, execute the following commands
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata[/I]
- Wait for a couple of minutes, once it is done. Now reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
- Once the installation is completed, enjoy the Oreo build OPS28.85-17 on your phone.
Or should I do the relatively easy OTA update described in here: https://forum.xda-developers.com/g5-plus/how-to/download-official-moto-g5-g5-plus-t3848246
since I seem to be running Indian firmware (92 instead of the 93 which I should be running for Europe).
Or is this way riskier with loss of IMEI etc. ?
Thanks in advance for your answer.
Click to expand...
Click to collapse
If you don't want to lose your data then go for OTA update, or if you want a clean installation of Oreo you can go for fastboot.(OTA update (this one)won't be detected if the software channel is different).and if you flash a different channel then the update time is different(future updates).

riyan65 said:
If you don't want to lose your data then go for OTA update, or if you want a clean installation of Oreo you can go for fastboot.(OTA update (this one)won't be detected if the software channel is different).and if you flash a different channel then the update time is different(future updates).
Click to expand...
Click to collapse
It took a while before I had the nerve to update, but I tried yesterday evening. I figured the best option would be to do the OTA update as described here: https://forum.xda-developers.com/g5-...-plus-t3848246
It worked like a charm, it updated my XT1685 to OPSS28.85-13 with reteu channel. After checking I received the October 1st 2018 security update and after that December 1st security update.
I am at OPSS28.85-13-5 at the moment.
So OTA updates work again.
I also tried the Lenovo Moto Smart Assistant again, but that still says unsupported device.
Thanks for your help and I hope this post is helping others too.

Confused74 said:
I also tried the Lenovo Moto Smart Assistant again, but that still says unsupported device.
Thanks for your help and I hope this post is helping others too.
Click to expand...
Click to collapse
LMSA did not recognize my device either, now it does. Don't exactly remember but I think it started working after I used the QR scan to dock the phone. You may want to give it a try if you have not already.

Moto G4 plus stuck in bootloader mode (Hard Brick)

Hi All.
I have unlock boot-loader and flash stock ROM after that i got an update (nougat 7.1) and I allowed.
after allowing my mobile stuck in bootloader and i am not able flash new images getting:
FAILED (remote failure)
finished. total time: 0.144s,
i tried all possible way.
for hard brick i followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but no success. please help me out.

If you're able to boot into the bootloader, then you're not hard bricked (fortunately).
What output do you get if you have your device in fastboot mode, then type 'fastboot getvar all' into the ADB terminal, then press enter?
If you can, use a different USB port and/or USB data cable.
Also, which firmware were you on? There is no 7.1 update for stock firmware, only 7.0 for Nougat or 8.1 for Oreo.

echo92 said:
If you're able to boot into the bootloader, then you're not hard bricked (fortunately).
What output do you get if you have your device in fastboot mode, then type 'fastboot getvar all' into the ADB terminal, then press enter?
If you can, use a different USB port and/or USB data cable.
Also, which firmware were you on? There is no 7.1 update for stock firmware, only 7.0 for Nougat or 8.1 for Oreo.
Click to expand...
Click to collapse
Below is the output of fastboot getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.06(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: d72acc4e
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: EC1CEC0000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.06-0-g0edfb0d
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.104s
and i flash nougat 7 then i got update, I allowed update and phone got stuck in bootloader.

What firmware are you trying to flash now? Looks like your main issue is that you do not have a GPT partition table on your device, so your device does not know what files to flash.
I would recommend downloading the Oreo firmware from here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip delete the old stock ROM files from your ADB folder and replace with the Oreo firmware files. Then try to flash the Oreo GPT file

Stuck on bootloader with NO OS and OEM_LOCKED -- (MOTOG4PLUS)
I am stuck on Bootloader with NO OS and OEM_LOCKED . The bootloader vers. it shows is
B1.06(*) (sha-0edfb0d, 2017-06-01 12:10:43)
When installing GPT.bin file it says FAILED TO INITIALISE PARTITION TABLE .
don't know what to do totally stuck .
Service Center was of no use .
PLS HELP ME OUT !!
SOS !!

viking_vikram said:
I am stuck on Bootloader with NO OS and OEM_LOCKED . The bootloader vers. it shows is
B1.06(*) (sha-0edfb0d, 2017-06-01 12:10:43)
When installing GPT.bin file it says FAILED TO INITIALISE PARTITION TABLE .
don't know what to do totally stuck .
Service Center was of no use .
PLS HELP ME OUT !!
SOS !!
Click to expand...
Click to collapse
What happened to your device before this?
Which GPT.bin are you trying to load up? Try the April 2018 GPT and bootloader https://drive.google.com/open?id=13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI or the December 2018 GPT and bootloader: https://drive.google.com/open?id=1TlFPYf4y3MEARFUuHSNB5Ty0GD-SQua-
However, if your device continues to report GPT partition initialisation errors, it's possible your flash storage is damaged and may require a motherboard replacement.

Where can I get a motherboard replacement ?
will it finally solve my problem ?

viking_vikram said:
Where can I get a motherboard replacement ?
will it finally solve my problem ?
Click to expand...
Click to collapse
Probaly a service centre would be the best place to request a motherboard replacement. It may solve your issue, however, as your G4 Plus is out of warranty, a motherboard replacement is not cheap - I've seen quotes for 8000-1000 rupees. Thus, you may wish to look into buying a new device altogether.

Bricked Moto G5 - Potter

Hi,
Good Morning All,
I have an old Moto G5+ (Potter, XT1686) which I use for streaming media. The phone was rooted and used to run Lineage / Pixel Experience ROMs and for some time it was rooted with Magisk.
I wanted to remove the root and return to official ROM and I followed all the published procedures but I am unable to get the system to boot.
If TWRP is installed - The phone reboots to TWRP despite installing all variants of Lineage / Pixel Experience.
If I try and install the official rom using fastboot commands the phone goes to the "no command" screen and remains stuck there.
fastboot oem fb_mode_set
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 dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
My fastboot getvar all output is as below:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2244SWST
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 7E5EF1BA00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358958067204534
(bootloader) meid:
(bootloader) date: 05-23-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Feb 21 20:41:18 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:8.1.0/O
(bootloader) ro.build.fingerprint[1]: PS28.85-17-6-2/77e7:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.261.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_46.55.07.90R POTTER_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g7b625a0 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Mon Mar 4 14:31:59 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=27e6e4b-dirty
(bootloader) devcfg.git: git=27e6e4b-dirty
(bootloader) keymaster.git: git=27e6e4b-dirty
(bootloader) cmnlib.git: git=27e6e4b-dirty
(bootloader) cmnlib64.git: git=27e6e4b-dirty
(bootloader) prov.git: git=27e6e4b-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.156s
Click to expand...
Click to collapse
Motorola Rescue and Smart Assistant is also unable to get me to boot; It goes to the "no Command" screen.
Any help would is appreciated !
Thanks.
Ravi