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

Moto G4 Plus fastboot brick

when i trying to install latest gpt.bin and bootloader and i try older also it is showing
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.078s
Bootloader
(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' (3651 KB)...
OKAY [ 0.126s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.263s
please help.

Which blankflash files are you using that are causing this error, the September 2017 or June 2017 ones?
You may wish to try the December 2017 GPT and bootloader files : https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80
If the December 2017 GPT/bootloader files work, then you will want to re-flash the NPJS25.93-14-13 stock ROM (mainly for Brazil, India, EU and UK users, may flash onto other region's devices) to fully repair: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

Likhith Emmanuel said:
when i trying to install latest gpt.bin and bootloader and i try older also it is showing
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.078s
Bootloader
(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' (3651 KB)...
OKAY [ 0.126s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.263s
please help.
Click to expand...
Click to collapse
Same error while unlocking bootloader..moto g4 xt1624

Samruddh said:
Same error while unlocking bootloader..moto g4 xt1624
Click to expand...
Click to collapse
Can I ask what steps you've tried when unlocking the bootloader please? Have you followed this guide, https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2 and if so, what errors are you getting? If you could, please post a screenshot of the error or the text of the error.
Is your device bought from a carrier (and thus carrier locked) or an Amazon Prime device or was it from Amazon/a retailer?
Could we see your getvar info please?
1)Boot your device to the bootloader. Connect via USB to your computer.
2)In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Paste the output into a post here please. You may wish to remove IMEI numbers.

echo92 said:
Can I ask what steps you've tried when unlocking the bootloader please? Have you followed this guide, https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2 and if so, what errors are you getting? If you could, please post a screenshot of the error or the text of the error.
Is your device bought from a carrier (and thus carrier locked) or an Amazon Prime device or was it from Amazon/a retailer?
Could we see your getvar info please?
1)Boot your device to the bootloader. Connect via USB to your computer.
2)In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Paste the output into a post here please. You may wish to remove IMEI numbers.
Click to expand...
Click to collapse
Yeah i ordered in amazon

Samruddh said:
Yeah i ordered in amazon
Click to expand...
Click to collapse
Okay, was it an Amazon Prime device (with the adverts on the lock screen) or just a retail device sold by Amazon?
As far as I know, the Amazon Prime version cannot have its bootloader unlocked, and Motorola won't issue an unlock key for such devices. You'll know if it's an Amazon Prime device from adverts on the lockscreen and if you go to Settings>About Phone, under software channel it'll say AMZ. On retail devices it'll be retin (retail India) or reteu (retail Europe) etc.

echo92 said:
Okay, was it an Amazon Prime device (with the adverts on the lock screen) or just a retail device sold by Amazon?
As far as I know, the Amazon Prime version cannot have its bootloader unlocked, and Motorola won't issue an unlock key for such devices. You'll know if it's an Amazon Prime device from adverts on the lockscreen and if you go to Settings>About Phone, under software channel it'll say AMZ. On retail devices it'll be retin (retail India) or reteu (retail Europe) etc.
Click to expand...
Click to collapse
Retin it is showing..pls do check attachment..help me with this..i want to root my phone to do customizations..im bored with this 7.0

Samruddh said:
Retin it is showing..pls do check attachment..help me with this..i want to root my phone to do customizations..im bored with this 7.0
Click to expand...
Click to collapse
Okay, and can you post the getvar info as previously requested please?
Can I ask what steps you performed to attempt to unlock your bootloader as well? I'd like to know how far you got so we can help you.

echo92 said:
Okay, and can you post the getvar info as previously requested please?
Can I ask what steps you performed to attempt to unlock your bootloader as well? I'd like to know how far you got so we can help you.
Click to expand...
Click to collapse
Ok ll execute getvar command soon..
I followed same steps as u shown in that link..
* Switched on developer option to enable oem unlocking n usb debugging
*Downloaded n installed sdk tools
*From motorola website Writing commands to unlock oem data by opening shift+right button command window
It always shows
Failed to get unlock data
0.350(some seconds)
Finished

Samruddh said:
Ok ll execute getvar command soon..
I followed same steps as u shown in that link..
* Switched on developer option to enable oem unlocking n usb debugging
*Downloaded n installed sdk tools
*From motorola website Writing commands to unlock oem data by opening shift+right button command window
It always shows
Failed to get unlock data
0.350(some seconds)
Finished
Click to expand...
Click to collapse
The same it shows as in the following attachment

Samruddh said:
Ok ll execute getvar command soon..
I followed same steps as u shown in that link..
* Switched on developer option to enable oem unlocking n usb debugging
*Downloaded n installed sdk tools
*From motorola website Writing commands to unlock oem data by opening shift+right button command window
It always shows
Failed to get unlock data
0.350(some seconds)
Finished
Click to expand...
Click to collapse
Can you try with the minimal ADB tools as well? https://forum.xda-developers.com/showthread.php?t=2317790 and with the minimal ADB tools, use 'fastboot oem get_unlock_data' without quotes.
Have you had your motherboard changed? If not, and you cannot get the unlock data, then you may have to post to the official Lenovo/Motorola forums: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
As requested in the first post of that page, please provide the getvar info and the result of the get_unlock_data (whatever it is) in your post, else the admin may not forward your request to the internal team.

Samruddh said:
I tried with adb tools and I've not changed motherboard..here s result of getvar
Click to expand...
Click to collapse
Hmm, you have a CID of 0x0000 which should be unlockable. I wonder what's happened to your ro.carrier though, that should read retin rather than unknown.
I'd post on the Lenovo/Motorola forum I linked above with the information requested in the opening post of that thread. By the way, you can copy by right clicking in the menubar of the command line window then going to Edit>Copy. Saves you having to take a screenshot and they'll want a text entry.

echo92 said:
Hmm, you have a CID of 0x0000 which should be unlockable. I wonder what's happened to your ro.carrier though, that should read retin rather than unknown.
I'd post on the Lenovo/Motorola forum I linked above with the information requested in the opening post of that thread. By the way, you can copy by right clicking in the menubar of the command line window then going to Edit>Copy. Saves you having to take a screenshot and they'll want a text entry.
Click to expand...
Click to collapse
Ok..ll paste the text info from next! Thanks!

echo92 said:
Hmm, you have a CID of 0x0000 which should be unlockable. I wonder what's happened to your ro.carrier though, that should read retin rather than unknown.
I'd post on the Lenovo/Motorola forum I linked above with the information requested in the opening post of that thread. By the way, you can copy by right clicking in the menubar of the command line window then going to Edit>Copy. Saves you having to take a screenshot and they'll want a text entry.
Click to expand...
Click to collapse
Any updates on this?

Samruddh said:
Any updates on this?
Click to expand...
Click to collapse
Did you post on the Lenovo/Motorola official forum thread as directed? They are the only ones likely to help you at this stage.
I see one new report from an athene device in the last few days, but that device is from Argentina. As an aside, that report has no IMEI, which may slow down the help to get their code.
Please post in the Bootloader Unlock thread on the Motorola/Lenevo forum, with the getvar info (with IMEI) and the result of the get_unlock_data as directed. They then should forward the message to their internal teams and look for an email response in 48-72 hours (or 2-3 working days).

facing same issue
anyone found solution for this?
i have an indian version xt1643
"failed to initialize partition table" main problem i guess
it'd be great if i get any help

Utcresta said:
anyone found solution for this?
i have an indian version xt1643
"failed to initialize partition table" main problem i guess
it'd be great if i get any help
Click to expand...
Click to collapse
Hmm, what have you tried so far? Can you describe what happened before experiencing this error?
Looking through your image, though it's quite low resolution, I see no entries in your firmware version or kernel or baseband, which suggests you used the blankflash at some point?

echo92 said:
Hmm, what have you tried so far? Can you describe what happened before experiencing this error?
Looking through your image, though it's quite low resolution, I see no entries in your firmware version or kernel or baseband, which suggests you used the blankflash at some point?
Click to expand...
Click to collapse
I had Resurrection Remix Oreo on the device. I was just using the phone casually with vanced youtube running on the background and facebook messenger too. Suddenly it froze so i tried to restart it but no response and then after some time the screen went blank. When plugged in to charge, the led glowed and screen was plain blank without the screen lighting up. So I googled and found the following thread.
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Followed the procedure then the screen was up again. The screen i got after doing this is below. Sorry for the low resolution hope you can understand it.
https://imgur.com/a/mAUFgiJ
IMEI is gone. It shows all 0s in the imei field. Tried flashing stock recovery, custom recovery, twrp no luck. The device is recognized as "fastboot athene_16mp S" when connected to pc.
Hope you can help.

Utcresta said:
I had Resurrection Remix Oreo on the device. I was just using the phone casually with vanced youtube running on the background and facebook messenger too. Suddenly it froze so i tried to restart it but no response and then after some time the screen went blank. When plugged in to charge, the led glowed and screen was plain blank without the screen lighting up. So I googled and found the following thread.
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Followed the procedure then the screen was up again. The screen i got after doing this is below. Sorry for the low resolution hope you can understand it.
https://imgur.com/a/mAUFgiJ
IMEI is gone. It shows all 0s in the imei field. Tried flashing stock recovery, custom recovery, twrp no luck. The device is recognized as "fastboot athene_16mp S" when connected to pc.
Hope you can help.
Click to expand...
Click to collapse
That isn't your actual fastboot mode. fastboot getvar will not show proper details. I too had tried and got imei as multiple 0 with "fastboot getvar", also had seen a lot of other things missing too.
Download and flash the latest stock nougat from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Before flashing stock rom, you will need to flash latest "bootloader" and "gpt". First flash bootloader and gpt and then reboot to bootloader (fastboot reboot bootloader).
Now you will have your original bootloader back. Now you can flash stock nougat rom and everything will be back to normal.
I hope you have not upgraded to soak test oreo by "locked bootloader" method because if you did then you will have to wait till fastboot rom for oreo comes out or ask someone who is on soak test oreo to provide their bootloader and gpt partitions (if they upgrades by locked bootloader method), as you wouldn't be able to flash nougat bootloader and gpt partitions.

i have a similar problem on my xt1643 as it is only booting to the locked bootloader, and tried all the gpt.bin till april 2018 while all the others gave the downgrade error, april 2018 gave the following error.
PS C:\adb> fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.086s
PS C:\adb>
---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------
Athul56 said:
i have a similar problem on my xt1643 as it is only booting to the locked bootloader, and tried all the gpt.bin till april 2018 while all the others gave the downgrade error, april 2018 gave the following error.
PS C:\adb> fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.086s
PS C:\adb>
Click to expand...
Click to collapse
PS C:\adb> 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-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB MICRON Q3J97V RV=08 PV=10 FV=00000000000000A2
(bootloader) ram: 3GB MICRON LP3 DIE=6Gb M5=03 M6=00 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223RFGVV
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: DB66230200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: *************
(bootloader) meid:
(bootloader) date: 01-07-2017
(bootloader) sku: XT1643
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Aug 2 4:37: 6 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.02R ATHENE_INDIA_
(bootloader) version-baseband[1]: DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-ge03508d-00131-g44
(bootloader) kernel.version[1]: 2576f ([email protected]) (gcc version
(bootloader) kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version[3]: :58:16 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retin
all: listed above

Moto g5 plus IMEI 0 after flashing anything? Read on!

After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required!
Prerequisites:
U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on other versions)
8.1 custom Oreo ROM (I used Validus, we only use this to get signal and imei back to default)
Moto g5 plus STOCK ROM https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Patience
***************************
That's it!
Down to the nitty gritty. Your imei is zero or 0000000 or some funky number, and no sim cards/cellular service works in your device, right? I finally found the simple solution after hard work. You have TWO options, read on.
1. Flash custom recovery, erase everything, and get on 8.1 Oreo ROM (delete modemst1 and 2 in fastboot beforehand) and STAY THERE. Signal will work.
2. OR go back to stock everything and locked bootloader, which is what I did. My fastboot says software status official oem locked and I get updates.
******************
The TRICK is, if your imei is 0 and cellular doesn't work, you have to delete your modemst1 and 2 in fastboot before installing anything new, so that it can reset back to default. The other TRICK is if you are reverting back to stock, follow all the normal commands for reflashing, but DON'T do anything with modemst. say I was following normal commands for flashing, then ran across these three commands....
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
SKIP THEM. What we're attempting to do is keep your EFS folder as it was on the 8.1 OREO, aka WORKING. Flashing rom itself doesn't delete the EFS folder, but when you run those commands (which is in most tutorials) IT WILL WRECK YOUR IMEI AGAIN.
************
So, to recap. To fix IMEI issue, use these two commands in fastboot
fastboot erase modemst1
fastboot erase modemst2
THEN, flash 8.1 custom oreo rom, and if you like it stay with it, your signal will be working again, or go back to stock everything oem locked, your choice, just make sure you don't delete your modemst1,2 in commands WHILST doing so.
And that's it! Your imei and signal is working again. What's stupid is that this happens in the first place, but life happens. FIXED!

Did you get voLTE to work?

What carrier are you on? I am on Verizon and this only gets me 3G like all of other fixes for this issue on here.

stonewolf05 said:
What carrier are you on? I am on Verizon and this only gets me 3G like all of other fixes for this issue on here.
Click to expand...
Click to collapse
Was with Verizon, was only getting 3g, frequent drops. Switched to AT&T just because they're so much better in my area.

thankyou soo much . helped me

I dint get my signal/IMEI back after installing custom rom
any suggestions??
Thanks in Advance

mohitzr said:
I dint get my signal/IMEI back after installing custom rom
any suggestions??
Thanks in Advance
Click to expand...
Click to collapse
Unfortunately, none of these methods work no more, the question is why?. Personally, I believe something further has been borked in oreo development, just like the volte issue. Absolutely no methods restore my ime, some actually make it very difficult to even get a signal now. I spent several hours last night trying every option available just to get a signal, whereas before I flashed the latest vladious rom, flashing pixel experience, or any oreo rom for that matter, would restore 4g on first boot. My ime is 0 and i give up. In all my years with android modding (since zte blade), I have never had a device with so many issues, and so unpredictable. You can use a method to fix something, and next thing you know it does not work, for example, encryption can be really hit and miss when you first flash twrp, even flashing no verity does not always work.

Tried every possible combination as per guides/fixes....no luck..

The only thing that's worked for me without fail every time is wiping everything with twrp, Dalvik, Data, System, Cache, internal storage, hitting that dreaded Format Data button, and flashing the earliest stock firmware (which I believe is 137-33 for the XT1687) using fastboot. Having a backup can save a ton of time and headaches too. If there's any point where you DO get at least LTE working, back up that EFS partition before you do ANYTHING else. But try flashing the earliest stock you can find, or preferably the one that was on your device when you bought it.

Worked like a Charm!
Dude, i was looking for the same since yesterday, come to this thread and follow all the steps carefully. My IMEI was showing 0 before and now everything is working fine including both SIM cards.
Thanks
beatlesfan5858 said:
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required!
Prerequisites:
U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on other versions)
8.1 custom Oreo ROM (I used Validus, we only use this to get signal and imei back to default)
Moto g5 plus STOCK ROM https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Patience
***************************
That's it!
Down to the nitty gritty. Your imei is zero or 0000000 or some funky number, and no sim cards/cellular service works in your device, right? I finally found the simple solution after hard work. You have TWO options, read on.
1. Flash custom recovery, erase everything, and get on 8.1 Oreo ROM (delete modemst1 and 2 in fastboot beforehand) and STAY THERE. Signal will work.
2. OR go back to stock everything and locked bootloader, which is what I did. My fastboot says software status official oem locked and I get updates.
******************
The TRICK is, if your imei is 0 and cellular doesn't work, you have to delete your modemst1 and 2 in fastboot before installing anything new, so that it can reset back to default. The other TRICK is if you are reverting back to stock, follow all the normal commands for reflashing, but DON'T do anything with modemst. say I was following normal commands for flashing, then ran across these three commands....
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
SKIP THEM. What we're attempting to do is keep your EFS folder as it was on the 8.1 OREO, aka WORKING. Flashing rom itself doesn't delete the EFS folder, but when you run those commands (which is in most tutorials) IT WILL WRECK YOUR IMEI AGAIN.
************
So, to recap. To fix IMEI issue, use these two commands in fastboot
fastboot erase modemst1
fastboot erase modemst2
THEN, flash 8.1 custom oreo rom, and if you like it stay with it, your signal will be working again, or go back to stock everything oem locked, your choice, just make sure you don't delete your modemst1,2 in commands WHILST doing so.
And that's it! Your imei and signal is working again. What's stupid is that this happens in the first place, but life happens. FIXED!
Click to expand...
Click to collapse

(bootloader) Permission denied. Please help
Can anyone help on this error. I'm having IMEI 0 error, was working fine in morning after that my friend messed up and now same error. I was not able to fire any command now. please help.
fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
Other might helpful info:
fastboot getvar all
(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 SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2245K4LB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 372C889E00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358958068640199
(bootloader) meid:
(bootloader) date: 07-20-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 6:53:42 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.14.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[0]: M8953_8000.128.06.42u POTTER_INDIADSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g708ac5e (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]: hu Jan 12 12:24:19 CST 2017
(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 (0)
(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.121s
beatlesfan5858 said:
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required!
Prerequisites:
U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on other versions)
8.1 custom Oreo ROM (I used Validus, we only use this to get signal and imei back to default)
Moto g5 plus STOCK ROM https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Patience
***************************
That's it!
Down to the nitty gritty. Your imei is zero or 0000000 or some funky number, and no sim cards/cellular service works in your device, right? I finally found the simple solution after hard work. You have TWO options, read on.
1. Flash custom recovery, erase everything, and get on 8.1 Oreo ROM (delete modemst1 and 2 in fastboot beforehand) and STAY THERE. Signal will work.
2. OR go back to stock everything and locked bootloader, which is what I did. My fastboot says software status official oem locked and I get updates.
******************
The TRICK is, if your imei is 0 and cellular doesn't work, you have to delete your modemst1 and 2 in fastboot before installing anything new, so that it can reset back to default. The other TRICK is if you are reverting back to stock, follow all the normal commands for reflashing, but DON'T do anything with modemst. say I was following normal commands for flashing, then ran across these three commands....
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
SKIP THEM. What we're attempting to do is keep your EFS folder as it was on the 8.1 OREO, aka WORKING. Flashing rom itself doesn't delete the EFS folder, but when you run those commands (which is in most tutorials) IT WILL WRECK YOUR IMEI AGAIN.
************
So, to recap. To fix IMEI issue, use these two commands in fastboot
fastboot erase modemst1
fastboot erase modemst2
THEN, flash 8.1 custom oreo rom, and if you like it stay with it, your signal will be working again, or go back to stock everything oem locked, your choice, just make sure you don't delete your modemst1,2 in commands WHILST doing so.
And that's it! Your imei and signal is working again. What's stupid is that this happens in the first place, but life happens. FIXED!
Click to expand...
Click to collapse

deep_raman said:
Can anyone help on this error. I'm having IMEI 0 error, was working fine in morning after that my friend messed up and now same error. I was not able to fire any command now. please help.
fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
Other might helpful info:
fastboot getvar all
(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 SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2245K4LB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 372C889E00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358958068640199
(bootloader) meid:
(bootloader) date: 07-20-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 6:53:42 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.14.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[0]: M8953_8000.128.06.42u POTTER_INDIADSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g708ac5e (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]: hu Jan 12 12:24:19 CST 2017
(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 (0)
(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.121s
Click to expand...
Click to collapse
Is your device got fixed?

riyan65 said:
Is your device got fixed?
Click to expand...
Click to collapse
No yet brother! I've to take it to the customer center but they are stating that it can't be solved through software and need to replace motherboard LOL.
I took back and its with me now. Waiting for some solutions here.

deep_raman said:
No yet brother! I've to take it to the customer center but they are stating that it can't be solved through software and need to replace motherboard LOL.
I took back and its with me now. Waiting for some solutions here.
Click to expand...
Click to collapse
Your network problem can be solved since IMEI no is shown getvar. You can try installing latest stock Oreo, or trying custom ROMS. Many times custom ROM bring back the IMEI.

riyan65 said:
Your network problem can be solved since IMEI no is shown getvar. You can try installing latest stock Oreo, or trying custom ROMS. Many times custom ROM bring back the IMEI.
Click to expand...
Click to collapse
Bro, I've tried and what I'm getting is below, i think becuase of flashing_locked:
fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.410s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.419s
fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.526s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.540s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 6.117s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.175s
I can't able to flash too

deep_raman said:
Bro, I've tried and what I'm getting is below, i think becuase of flashing_locked:
fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.410s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.419s
fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.526s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.540s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 6.117s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.175s
I can't able to flash too
Click to expand...
Click to collapse
Did you try Lenovo moto smart assistant? It will flash the device for you.

riyan65 said:
Did you try Lenovo moto smart assistant? It will flash the device for you.
Click to expand...
Click to collapse
Yeah , tried that as well. It is failing at 67%. Tried in USB debugging as well as fastboot mode.!!

deep_raman said:
Yeah , tried that as well. It is failing at 67%. Tried in USB debugging as well as fastboot mode.!!
Click to expand...
Click to collapse
Use the firmware downloaded by LMSA and flash the device manually. And did you try any custom ROMs? Mostly they help you to get back your IMEI.

riyan65 said:
Use the firmware downloaded by LMSA and flash the device manually. And did you try any custom ROMs? Mostly they help you to get back your IMEI.
Click to expand...
Click to collapse
I tried the LMSA and custom ROMS but the main problem is I dont even have flashing permission too. As mentioned earlier I' m getting flashing permission denied. I dont have TWRP install, dont have flashing permission...!! So cant flash anything anymore !!! :crying:

deep_raman said:
I tried the LMSA and custom ROMS but the main problem is I dont even have flashing permission too. As mentioned earlier I' m getting flashing permission denied. I dont have TWRP install, dont have flashing permission...!! So cant flash anything anymore !!! :crying:
Click to expand...
Click to collapse
Solution
I was using previous/old version of ADB files(Fastboot.exe and ADB.exe). Post downloading latest version, I was able to fire below command through bootloader:
fastboot.exe flashing unlock
Now I'm all happy.

slot-count not found, slot-suffixes not found,bootloaer working fine

Hello,
I've recently tried to flash stock recovery to be able to receive update . I had TWRP installed already . But whenever I type fastboot command , I get error like slot-count not found .
And that's not the case . I've tried with flashing bootloader and gpt.bin as well and get the same error ! My bootloader is working fine! Also whenever I try these steps, I end up losing my WiFi/hotspot connectivity !
Here take a look . I get these errror in ADB :
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe O
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\User
s\MAYUR Desktop\New folder recovery.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
bootloader) slot-suffixes: not found
(bootloader) has-slot recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.529s]
writing 'recovery'..
<bootloader) Image signed with key bad key
OKAY [ 9.668s]
finished. total time: 1.204s
rs\MAYUR\Desktop\New folder\gpt.bin"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition "C:\Use
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
<bootloader) slot-suffixes: not found
(bootloader) has-slot: partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing partition'.
(bootloader) Flashing prinary GPT image..
(bootloader) Flashing backup GPT image...
OKAY [ 9.093s]
finished. total time: 0.106s
C:\Program Files (x86)\Minimal ADB and Fastboot >fastboot flash bootloader "C:\US
ers\MAYUR Desktop\New folder\bootloader.img'
(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' (3651 KB)...
OKAY [ 0.124s]
writing 'bootloader'.
(bootloader) validating: bootloader.default.xml
(bootloader will pass: flash:aboot
<bootloader) will pass: flash:tz
(bootloader) will pass: flash: rpm
(bootloader) will pass: flash: hyp
(bootloader will pass: flash: keymaster
(bootloader) will pass: flash:cmnlib
(bootloader will pass: flash sbli
(bootloader) committing: bootloader.default.xml
bootloader> flashing 'emmc_apps boot.mbn' to 'abooty
(bootloader) flashing 'tz.mbn' to 'tz'
<bootloader) flashing rpm.mbn' to rpm'
(bootloader) flashing 'hyp.mbn' to 'hyp'
(bootloader flashing 'keymaster.mbn' to 'keymaster'
bootloader) flashing 'canlib.mbn' to 'canlib'
OKAY [ 0.608s]
(bootloader) flashing 'sbll.mbn' to sbli'
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
(Getvar all) returned this : ?
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe
C:\Users\MAYUR\Desktop\New folder>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-nsm8952-B1.07
bootloader) product: athene 16mp
<bootloader board: athene_16mp
<bootloader) secure yes
<bootloader) hwrey: P2A
<bootloader) radio: 4
<bootloader) storage-type ennc
<bootloader) emnc 16GB SAMSUNG QE13MB RU-08 PU-7 FU-OOOOOOOOOOOOOOOD
<bootloader) ran: 2GB SAMSUNG LP3 DIE=8Gb M501 M6-05 M2=00 M8 -17
(bootloader) cpu MSM8952
(bootloader) serialno: *protected*
<bootloader) cid: Ox0032
<bootloader) channelid: Oxco
(bootloader) uid: 2E2FAAOOOOOOOOOOOOOOOOOOO000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvo id: yes
(bootloader) reason: Volume down key pressed
bootloader> max-download-size: 536870912,
<bootloader) meid:
(bootloader) imei: *protected*
<bootloader) date: 05-31-2016
<bootloader) sku: XT1643
<bootloader) battid: SNN5966A
bootloader> max-sparse-size: 268435456
<bootloader) iccid:
<bootloader) cust_md5:
(bootloader> current-time "'Sat Apr 30 0:19:14 UTC 2016"
(bootloader) ro.build.fingerprint [0]: motorola/athene/athene:2.0/NPJS25.
bootloader) ro.build.fingerprint(1): 93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
bootloader) ro.build.version.full[1]: il.en.US
bootloader) version-baseband: M8952_70030.25.03.62.02R DFLT_FSG
(bootloader) kernel.version [1]: 2526f <hudsoncneilclbld72) (gcc version
<bootloader) ro.build.version.qcon: LA.BR.1.3.6-01210-8926.0
bootloader) kernel.version [0]: Linux version 3.10.84-ge03508d-00131-944,
bootloader) kernel.version [2]: 4.8 (GCC) > 111 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version [3]: :58:16 CDT 2018
(bootloader) tz.git: git-69dd24b-dirty
(bootloader) rpm.git: [email protected]
<bootloader) sbl1.git: git-MBM-NG-UB1.07-6-952d1343
(bootloader) hyp.git: git-69dd24b-dirty
(bootloader) cmnlib.git:git-69dd24b-dirty
(bootloader) aboot.git: git-MBM-NG-UB1.07-0-9f9b89ba
bootloader> keymaster-git: git-69dd24b-dirty
(bootloader) ro.carrier: retin
(bootloader) frp-state: no protection (0)
<bootloader> qe: qe 0/1
all: listed above
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
I've read all the related forum but none of them is similar to mine ! They say we've have to blank flash the bootloader . But mines working fine . Do I really need to blank flash or something else would work fine ? If i really need to blank flash , then pls guide me !
Thank you very much in advance !
Have a great day ?
P.S. = sorry if the related thread already exist !

As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912

Sir I've flashed RR, INVICTA,and many other ROMs but... Didn't face this issue before ... I've recently flashed stock firmware provided by @rajatgupta1998 in this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/amp/ .. and ended up here !! The thread you provided as reference is an older discussion where he downgraded his bootloader by flashing ROM from different Android version ... But I've done nothing like that ! Please help me how to het the radio working ! Thanks in advance sir !

echo92 said:
As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912
Click to expand...
Click to collapse
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply ??

Vs1607 said:
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply
Click to expand...
Click to collapse
Does your computer detect your device when you connect via USB whilst booted in TWRP (does your device appear in Device Manager if you're using Windows?) and what version of TWRP are you using? What version of fastboot/ADB do you have installed on your computer?
I'm not that familiar with helping to losing baseband - that's why I referred you to that thread - though it's old and perhaps not exactly what happened to your device, there may be some useful information as to fixing your device.

Another noobie needs assistance - HTC upgrade gone wrong.

Hello, and thank you in advance for your assistance.
I bought a "new" Verizon HTC 10 off Ebay. It seemed to be a stock phone, with version 2.4xxxx; I am not exactly sure which version. I have bought my 2 daughters HTC 10's as well. There's are fine. They both have version 3.xxxx. I thought to upgrade my phone to somewhere around their version, because my phone seemed to have connectivity issues when both Wi-Fi and Data were enabled at the same time. However, the OS said they were no new updates for the phone. I checked the HTC site and they had the 2.51.617.32 RUU available. It said it would wipe all data, but that was no consequence to me because I didn't want to save anything. I didn't make a recovery backup (Stupid)! I downloaded the RUU, started it, and it errored out at about 90%; Erro 155: Unknown Error - The ROM update utility cannot update your Android phone. Please get the correct ROM update utility and try again. After that, on reboot the phone constantly reboots. I stop it by booting into download mode. Then choosing "power off". Since then, I have tried the RUU several more times, I have downloaded it again just to make sure I had an uncorrupted exe, I put in on my SD card and tried to update it that way: E: Signature Verification failed - error 21. I have tried the 3.6xxxx update from one of the people on this site. I get all the same messages. Also, I have used htc_fastboot to see if that would work. It errors out at 90% as well at tp_syn3708.img error. I have taken it to a repair shop, but they weren't able to fix it. I have chatted back and forth with HTC support. They had me change the CID to BS_US001. That did nothing. I read more on this forum and changed the CID to VZ_001. That didn't change anything. At this point, what are my options? I'm using an older backup phone, but I hope I can "reboot" this one. Thanks again.

Byrdman2b said:
Hello, and thank you in advance for your assistance.
I bought a "new" Verizon HTC 10 off Ebay. It seemed to be a stock phone, with version 2.4xxxx; I am not exactly sure which version. I have bought my 2 daughters HTC 10's as well. There's are fine. They both have version 3.xxxx. I thought to upgrade my phone to somewhere around their version, because my phone seemed to have connectivity issues when both Wi-Fi and Data were enabled at the same time. However, the OS said they were no new updates for the phone. I checked the HTC site and they had the 2.51.617.32 RUU available. It said it would wipe all data, but that was no consequence to me because I didn't want to save anything. I didn't make a recovery backup (Stupid)! I downloaded the RUU, started it, and it errored out at about 90%; Erro 155: Unknown Error - The ROM update utility cannot update your Android phone. Please get the correct ROM update utility and try again. After that, on reboot the phone constantly reboots. I stop it by booting into download mode. Then choosing "power off". Since then, I have tried the RUU several more times, I have downloaded it again just to make sure I had an uncorrupted exe, I put in on my SD card and tried to update it that way: E: Signature Verification failed - error 21. I have tried the 3.6xxxx update from one of the people on this site. I get all the same messages. Also, I have used htc_fastboot to see if that would work. It errors out at 90% as well at tp_syn3708.img error. I have taken it to a repair shop, but they weren't able to fix it. I have chatted back and forth with HTC support. They had me change the CID to BS_US001. That did nothing. I read more on this forum and changed the CID to VZ_001. That didn't change anything. At this point, what are my options? I'm using an older backup phone, but I hope I can "reboot" this one. Thanks again.
Click to expand...
Click to collapse
VZ__001
That's two underscores, not one.
That should work using the Verizon Oreo RUU, if it's indeed a Verizon model and the MID matches.
Although I feel you've already done too many changes for this information to be accurate, paste the output of:
fastboot getvar all
Remove the serial and imei for security purposes.
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
VZ__001
That's two underscores, not one.
That should work using the Verizon Oreo RUU, if it's indeed a Verizon model and the MID matches.
Although I feel you've already done too many changes for this information to be accurate, paste the output of:
fastboot getvar all
Remove the serial and imei for security purposes.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno:
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei:
(bootloader) version-main: 3.18.605.13
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: VZW__001
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.244s

Byrdman2b said:
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno:
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei:
(bootloader) version-main: 3.18.605.13
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: VZW__001
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.244s
Click to expand...
Click to collapse
You need the VZW Oreo RUU.
https://forum.xda-developers.com/showthread.php?p=70340077
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
You need the VZW Oreo RUU.
https://forum.xda-developers.com/showthread.php?p=70340077
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yes - I have already tried this one. Using htc_fastboot, this is the one that errors out on tp_syn3708. Should I download the file again and repeat the procedure?

Byrdman2b said:
Yes - I have already tried this one. Using htc_fastboot, this is the one that errors out on tp_syn3708. Should I download the file again and repeat the procedure?
Click to expand...
Click to collapse
Try using SD card method and verify the md5 sum of the download and/or redownload if need be.
Sent from my Pixel 3 XL using Tapatalk

​
santod040 said:
Try using SD card method and verify the md5 sum of the download and/or redownload if need be.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
What is the command to verify the md5 sum of the download?

Byrdman2b said:
​
What is the command to verify the md5 sum of the download?
Click to expand...
Click to collapse
On Linux:
md5sum filename.zip
Replace filename with actual name of file.
On Windows:
CertUtil -hashfile <path to file> MD5
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
On Linux:
md5sum filename.zip
Replace filename with actual name of file.
On Windows:
CertUtil -hashfile <path to file> MD5
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Here is what I get after downloading (again), MD5sum checking, and sending the file through fastboot:
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.18.605.13
found large-zip header, file count: 29
processing file 1/29...
sending 'zip' (113449 KB)...
OKAY [ 5.377s]
writing 'zip'...
(bootloader) HOSD CL#1016573
(bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) WARN Skip partition_info due to unmatched partition name
(bootloader) WARN Skip lockbooter.img due to unmatched partition name
(bootloader) WARN Skip backup_android-info.txt due to unmatched partitio
(bootloader) n name
(bootloader) get 32 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) boot_sign[email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 7.979s
preupdate done, rebooting...
resending command...
< waiting for device >
sending 'zip' (113449 KB)...
OKAY [ 5.427s]
writing 'zip'...
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_s
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP ERROR CODE, 22
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 7.544s
htc_fastboot finished. total time: 32.112s
I'll get in on the SD card and try it as well.

Byrdman2b said:
Here is what I get after downloading (again), MD5sum checking, and sending the file through fastboot:
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.18.605.13
found large-zip header, file count: 29
processing file 1/29...
sending 'zip' (113449 KB)...
OKAY [ 5.377s]
writing 'zip'...
(bootloader) HOSD CL#1016573
(bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) WARN Skip partition_info due to unmatched partition name
(bootloader) WARN Skip lockbooter.img due to unmatched partition name
(bootloader) WARN Skip backup_android-info.txt due to unmatched partitio
(bootloader) n name
(bootloader) get 32 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 7.979s
preupdate done, rebooting...
resending command...
< waiting for device >
sending 'zip' (113449 KB)...
OKAY [ 5.427s]
writing 'zip'...
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_s
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP ERROR CODE, 22
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 7.544s
htc_fastboot finished. total time: 32.112s
I'll get in on the SD card and try it as well.
Click to expand...
Click to collapse
Update-
When trying to update from SD card, I get the message:
E: footer is wrong
Update Package verification took 0.2 s (result 1)
E: Signature verification failed
E: Error 21
Installation aborted

Byrdman2b said:
Update-
When trying to update from SD card, I get the message:
E: footer is wrong
Update Package verification took 0.2 s (result 1)
E: Signature verification failed
E: Error 21
Installation aborted
Click to expand...
Click to collapse
You're using Download mode to install via SD card method, as stated in my stock thread, where firmware is posted, right?
Sounds like you're trying to flash via stock recovery, which is not the correct procedure...
Sent from my Pixel 3 XL using Tapatalk

I used Recovery mode (not download mode) to apply the update from SD card. Is this the correct procedure?

Byrdman2b said:
I used Recovery mode (not download mode) to apply the update from SD card. Is this the correct procedure?
Click to expand...
Click to collapse
No, check my post for flashing firmware via SD card method in the same thread, second post.
Same process applies to flashing an RUU.
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
No, check my post for flashing firmware via SD card method in the same thread, second post.
Same process applies to flashing an RUU.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Success!!!!!!! Success!!!!! I flashed it from SD, from bootloaded mode, and it worked properly. My phone is up and running now. Wow, I thought I would have to purchase another one. I am very grateful to you Sir. You are the 3rd person that I have worked with in order to get this phone working. I even took it to a shop where they repair phones, but they still couldn't get it working. Thank you for your help.

Byrdman2b said:
Success!!!!!!! Success!!!!! I flashed it from SD, from bootloaded mode, and it worked properly. My phone is up and running now. Wow, I thought I would have to purchase another one. I am very grateful to you Sir. You are the 3rd person that I have worked with in order to get this phone working. I even took it to a shop where they repair phones, but they still couldn't get it working. Thank you for your help.
Click to expand...
Click to collapse
No problem.
I'm glad to hear it worked out for you. [emoji106]
Sent from my Pixel 3 XL using Tapatalk

I know that it might be wrong to post here but, also i got one from eBay too. Phone was on Nougat and working fine, updated to Oreo when i turned on the Wifi on home. Oreo update begins and was working fine, except that on the lockscreen it was showing two cities instead of one... I tried everything to set it one one city but i couldn't figure what was wrong. So i decided to wipe it to factory reset. And then the problems begins... I notice that the battery drains so fast that i don't know why or what is causing that stuff... I charge it by quick charge and low charge and it's the same battery life just go around 11 or less hours. And it is always warn doing nothing, just lying around there. I had wiped and even installed the RUU from an external SD and the issue continues...
Also i had to rename the zip because i had the same error 21 and i changed the name and worked