Develop Bugs

I bricked my z play

Dear all,
after a try to load the Chinese twp and root my z play I bricked my phone. Now the only think that I can get is fast boot screen that says:
bl:co.14
baseband: not found
product: xt1635-02 32gb p7
serial number:
.
.
.
flashing_unlocked
.
.
I am trying to load the XT1635-02_ADDISON_RETUS_6.0.1_MPNS24.104-49-4 firmware by running a bat file that I found somewhere around with the following commands:
echo off
fastboot getvar max-sparse-size
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase DDR
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
But I get a screen says erasing... and the boot loop!!!
ANY IDEAS GUYS??
thx in advance for your help!!!:crying::crying::crying::crying:

asprofridis said:
Dear all,
after a try to load the Chinese twp and root my z play I bricked my phone. Now the only think that I can get is fast boot screen that says:
bl:co.14
baseband: not found
product: xt1635-02 32gb p7
serial number:
.
.
.
flashing_unlocked
.
.
I am trying to load the XT1635-02_ADDISON_RETUS_6.0.1_MPNS24.104-49-4 firmware by running a bat file that I found somewhere around with the following commands:
echo off
fastboot getvar max-sparse-size
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase DDR
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
But I get a screen says erasing... and the boot loop!!!
ANY IDEAS GUYS??
thx in advance for your help!!!:crying::crying::crying::crying:
Click to expand...
Click to collapse
Just flash the boot.img, recovery.img , all sparsechunks.img and the OEM.img using fastboot.
After you've flashed type in fastboot erase userdata and then fastboot reboot and see what happens
Sent from my XT1635-02 using XDA-Developers Legacy app
---------- Post added at 09:25 PM ---------- Previous post was at 09:23 PM ----------
You should never flash using a short cut or a bat file found in some obscure thread or website
Sent from my XT1635-02 using XDA-Developers Legacy app

Is the device recognized by fastboot?
Command: fastboot devices

Guys, I have a similar problem.
After an update of the android give error, I can no longer connect my moto z play.
Nor in fastboot and adb enters.
See video:
http://youtu.be/o8yYn0hNers

Luiz_Pennywise said:
Guys, I have a similar problem.
After an update of the android give error, I can no longer connect my moto z play.
Nor in fastboot and adb enters.
See video:
http://youtu.be/o8yYn0hNers
Click to expand...
Click to collapse
Oh man, the same problem here. I was updating the android for N and when restart the phone doesn't turn on, I'm crazy because I don't find anything to fix :crying::crying::crying::crying:

Luiz_Pennywise said:
Guys, I have a similar problem.
After an update of the android give error, I can no longer connect my moto z play.
Nor in fastboot and adb enters.
See video:
http://youtu.be/o8yYn0hNers
Click to expand...
Click to collapse
kaue152 said:
Oh man, the same problem here. I was updating the android for N and when restart the phone doesn't turn on, I'm crazy because I don't find anything to fix :crying::crying::crying::crying:
Click to expand...
Click to collapse
Have you guys downgraded to Marshmallow, then tried updating to N again? Particularly after installing the April update?

IncendiaryPyro said:
Have you guys downgraded to Marshmallow, then tried updating to N again? Particularly after installing the April update?
Click to expand...
Click to collapse
How should I do this? I was reading this topic https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
and they said that necessary download russian firmware, is it right?

kaue152 said:
How should I do this? I was reading this topic https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
and they said that necessary download russian firmware, is it right?
Click to expand...
Click to collapse
I'm not sure. I believe you need a blankflash file for that firmware from what I've gathered, if it was a downgrade to Marshmallow after the April update for N, then updating back to N.

IncendiaryPyro said:
I'm not sure. I believe you need a blankflash file for that firmware from what I've gathered, if it was a downgrade to Marshmallow after the April update for N, then updating back to N.
Click to expand...
Click to collapse
I'm was updating for Nougat, probabily was that April update. Honestly I don't know what to do

kaue152 said:
I'm was updating for Nougat, probabily was that April update. Honestly I don't know what to do
Click to expand...
Click to collapse
Have you ever downgraded to Marshmallow at any time before that happened?

IncendiaryPyro said:
Have you ever downgraded to Marshmallow at any time before that happened?
Click to expand...
Click to collapse
Yep, I'm was using ViperOS, I'm downgraded to stock Marshmallow and was doing the OTA updates. When the phone reboot to install Nougat this happened.

kaue152 said:
Yep, I'm was using ViperOS, I'm downgraded to stock Marshmallow and was doing the OTA updates. When the phone reboot to install Nougat this happened.
Click to expand...
Click to collapse
Ah, so it was the update to Nougat that caused it. Yeah that has something to do with a bootloader upgrader in the April update I believe. You'll have to wait for a blankflash file to surface to repair that issue, unfortunately. Only reason I was asking was because I downgraded to Marshmallow a few months ago, then OTA'd back to Nougat, then also got the March update later down the road and never had any issues. I haven't gotten the April update yet but it'll be a good reminder to me not to downgrade to Marshmallow again.

IncendiaryPyro said:
Ah, so it was the update to Nougat that caused it. Yeah that has something to do with a bootloader upgrader in the April update I believe. You'll have to wait for a blankflash file to surface to repair that issue, unfortunately. Only reason I was asking was because I downgraded to Marshmallow a few months ago, then OTA'd back to Nougat, then also got the March update later down the road and never had any issues. I haven't gotten the April update yet but it'll be a good reminder to me not to downgrade to Marshmallow again.
Click to expand...
Click to collapse
How did you fix it? I found a blankflash and another rom to install

kaue152 said:
How did you fix it? I found a blankflash and another rom to install
Click to expand...
Click to collapse
I never had to fix it. I downgraded from the January patch for N (which I had sideloaded), OTA'd from Marshmallow to N + the February patch from my carrier, then I got prompted for March's update a few weeks later, so I guess there was never an issue downgrading back then, but something changed in April's patch that causes hardbricks when you downgrade and try to go back to Nougat. I've never had the April patch installed before so it hasn't affected me. From what I've read, it's only happened to people who had downgraded after installing April's update. Sorry I can't offer any help there. :/

PLEASE ALL GO TO THIS LINK
Http://lenovo-forums.ru/topic/20594-moto-z-play-obschaya-tema-voprosov-i-otvetov/#comment-550611
WHILE MORE OF US SEE AND LEN LIKE THE COMMENT OF
* VVizard @
SAGE
THEY COULD HELP US CHECK IT

Hello there. So, after flashing the TWRP my moto z play got bricked and now it remains at the "bad key" screen at boot. I can get into the fastboot screen and the recovery. To my understanding, I need to flash some firmware. My doubts are; does it matter which one of all I flash? And, most are marshmallow: I had nougat before this happened so, will I have trouble flashing these? Thanks!

Kon22 said:
Hello there. So, after flashing the TWRP my moto z play got bricked and now it remains at the "bad key" screen at boot. I can get into the fastboot screen and the recovery. To my understanding, I need to flash some firmware. My doubts are; does it matter which one of all I flash? And, most are marshmallow: I had nougat before this happened so, will I have trouble flashing these? Thanks!
Click to expand...
Click to collapse
Flash only system, data and boot. Do not mess with the modem, efs and bootloader images.

[GUIDE] Unbrick MOTO Z Play.... work in progress! (not working yet)
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492

Moto z play updated blankflash
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19
Go here .. flash the files and thank god and the OP.

How to restore to stock?

I am using a rooted Z Play XT1635-02 and would like to un-root the device and restore it to stock. Can someone recommend a thread for me to follow. Thanks

[email protected] said:
I am using a rooted Z Play XT1635-02 and would like to un-root the device and restore it to stock. Can someone recommend a thread for me to follow. Thanks
Click to expand...
Click to collapse
download ROM from here[1] ( select appropriate country/region )
[1] https://mirrors.lolinet.com/firmware/moto/addison/official/
for flashing instructions ..go here [2]
[2] https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486

jatinkhatri said:
download ROM from here[1] ( select appropriate country/region )
[1] https://mirrors.lolinet.com/firmware/moto/addison/official/
for flashing instructions ..go here [2]
[2] https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
Is this finally the SIGNED stock firmware? I've been dying to have it since I know the unsigned won't allow you to relock the bootloader.

Euroter said:
Is this finally the SIGNED stock firmware? I've been dying to have it since I know the unsigned won't allow you to relock the bootloader.
Click to expand...
Click to collapse
You'll never relock your bootloader , it's over and I can't understand why people think it makes a difference, moto has given you the unlocking key by asking for that key you are unlocked and unlock forever.
Read the unlocking agreement page from moto. You signed off on it.
You'll never ever see signed firmware from moto anyways , they keep them in house, all you'll ever see is unsigned firmware packages.

https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118

Euroter said:
Is this finally the SIGNED stock firmware? I've been dying to have it since I know the unsigned won't allow you to relock the bootloader.
Click to expand...
Click to collapse
Nope...

core720 said:
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Click to expand...
Click to collapse
Please help. I successfully unlock bootloader and twrp but my big mistake was i erase user data via fastboot. My phones memory is empty. I tried to adb push zip file and whenever i flash it via twrp error says unable to mount data. I want to return in stock can u help me flashing/unbricking my mzp? I have the Android N firmware from russia. Can u teach me a step by step guide how should i survive my phone pleaseeeeee... thanks in advance

Kap_Tutan said:
Please help. I successfully unlock bootloader and twrp but my big mistake was i erase user data via fastboot. My phones memory is empty. I tried to adb push zip file and whenever i flash it via twrp error says unable to mount data. I want to return in stock can u help me flashing/unbricking my mzp? I have the Android N firmware from russia. Can u teach me a step by step guide how should i survive my phone pleaseeeeee... thanks in advance
Click to expand...
Click to collapse
Download the stock ROM ...extract it and run following commands turn by turn from the extracted folder ( you must have ADB tools installed )
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 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 system system.img_sparsechunk.9
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps

jatinkhatri said:
Download the stock ROM ...extract it and run following commands turn by turn from the extracted folder ( you must have ADB tools installed )
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 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 system system.img_sparsechunk.9
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps
Click to expand...
Click to collapse
Hi sir one of my friend telling that i dont need to flash the bootloader.img because it will make my device brick. He means that downgrading bootloader will be a problem? Please confirm

Kap_Tutan said:
Hi sir one of my friend telling that i dont need to flash the bootloader.img because it will make my device brick. He means that downgrading bootloader will be a problem? Please confirm
Click to expand...
Click to collapse
Yeah ...that can happen if you are on newer bootloader
So Skip bootloader.img

Moto Z Play Bricked
I have Moto Z Play. My device is totally bricked. When i try to boot my device it wont boot. Even fastboot mode wont work. When I connect this device to laptop, in device manager it shows Qualcomm HS-USB QDLoader 9008 & Notification LED Beside front Camera Constantly Starts Blinking. I had tried all the methods shown on XDA but i didnt find any solution from it.
If any one of a member from XDA knows this solution then please tell me.
Contact no- +91 9970631435
email- [email protected]
name- Mohammadzain Thakur

I want LOS14.1 on my phone, but it's better to keep on stock 7.1.1? Normally you are right, because it's stupid to change the rom just because the number (7.1.1 to 7.1.2).

Stock Recovery Issue

Everytime i try and flash the stock image in fastboot it fails when it gets to anything pertaining to the bootloader
FAILED (remote: Do not allow to flash Bootloader image on Unlock device)
My device is unlocked but to try and compat this i even try to re-lock the device which also fails:
FAILED (remote: oem lock back is forbidden)
Im stuck, i cant use the flashall because it fails, i cant individually flash files because the bootloader items fail,
im at a loss as to what to do.
Im able to flash a custom recovery but i cant do anything with it, except try and flash modem items with twrp which also did nothing.

brother, i am sorry for your condition , i dont have much knowledge on such things, but i once had MotoG, i used to flash Stock files with this method..
https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
if you are flashing Stock files, then Bootloader need not to be stayed UNLOCKED..
hope you get any idea from there.. all the best
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
look in to this also :
https://forum.xda-developers.com/mo...e-restore-moto-e-2015-stock-firmware-t3054303
this might give u anyidea

Did you have TWRP installed before you tried to flash stock Rom ? I'm guessing thats why its failing , but i dont know how to fix

maybe you're trying to flash older version of bootloader than the one you've already got? besides you don't need to flash bootloader to lash the rest, like system, modem or kernel

Okay so i know what my problem is i just dont know how to solve it:
I have a partially unlocked bootloader. is i do the fastboot oem device-info command, it tells me that my bootloader is unlocked but im unable to flash bootloader images (Device critical unlocked: false)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Device Secure boot: yes
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.080s]
finished. total time: 0.081s
Does anyone know how to get Device critical unlocked: true?

I stuck in the bootanimation and i cant flash a stock rom because there is no such thing. I found one, but this is no flashable zip. And the "flashall.bat" doesnt work. CM also doesnt work. I dont know what to do now.
Edit: Now i dont get into twrp recovery. With adb and with the hardware its not possible to enter twrp.

Did anyone found any solution? I am in same situation...

Found
flash only boot and system, not bootloader

finally while Flashing stock, i am stuck at Bootlogo looop
any suggestions??
i tried unrooting my RR 7.1.1 but with the zip provided , i think it failed..
any way to clean flash / freshly load stock again !!

nandakis4 said:
finally while Flashing stock, i am stuck at Bootlogo looop
any suggestions??
i tried unrooting my RR 7.1.1 but with the zip provided , i think it failed..
any way to clean flash / freshly load stock again !!
Click to expand...
Click to collapse
if you have the stock rom just follow the trouble shooting guide at the start of this thread , should work

Hi, thanks for replying..
flashed the files again,
Boot, recovery, then systemchunk files, REBOOT..
its still bootlooping, i think i am missing any file that needs to be put, but i am not putting .. !!
any more suggestions ??

nandakis4 said:
Hi, thanks for replying..
flashed the files again,
Boot, recovery, then systemchunk files, REBOOT..
its still bootlooping, i think i am missing any file that needs to be put, but i am not putting .. !!
any more suggestions ??
Click to expand...
Click to collapse
I am having the same issues:
I cannot flash anything pertaining to the bootloader, this is the official flash list, open fastboot and paste this entire list, when its finished you will see "failed" next to anything pertaining to the bootloader. And therein lies the issue, i havent found a soloution and ive been searching for 2 months now
fastboot flash partition gpt_both0.bin
fastboot flash sec sec.dat
fastboot flash apdp dp_AP_signed.mbn
fastboot flash msadp dp_MSA_signed.mbn
fastboot flash prov prov32.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devcfgbak devcfg.mbn
fastboot flash lksecapp lksecapp.mbn
fastboot flash lksecappbak lksecapp.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash cache cache.img
fastboot erase userdata
FYI i have unlocked my bootloader, and it wont let me lock it again

@nandakis4 Did you manage to solve your issue?
@itsjustbilly Why are you flashing the bootloader? It will fail if it's unlocked.
I'd want to go back to stock to start off fresh, but these are some discouraging stories.

cyrrrinda said:
Found
flash only boot and system, not bootloader
Click to expand...
Click to collapse
Please confirm if you were able to revert to MM without losing your signal.
Edit: It crossed my mind just now. TWRP has the ability to backup the modem so surely you could use it if you were to have problems with the signal later? Provided you can access the recovery of course, but that doesn't seem to be a problem in most cases.

qcn backup
Hi here is qcn backup from working phone. To go to engeneering mode you have to press ####8899#. Smaller is from qfil tool, bigger is from qpst tool (software download). When I restored, I am back on internet 4G, can make or receive calls, BUT NO SOUND from speaker and MIC not working so. Any idea?

cyrrrinda said:
Hi here is qcn backup from working phone. To go to engeneering mode you have to press ####8899#. Smaller is from qfil tool, bigger is from qpst tool (software download). When I restored, I am back on internet 4G, can make or receive calls, BUT NO SOUND from speaker and MIC not working so. Any idea?
Click to expand...
Click to collapse
Do 2G and 3G work? My phone can detect 4G, but not 2G and 3G.
You've probably solved the sound issue by now, otherwise have a look at this thread.

Stuck in bootloader and getvar all empty

Hello everyone,
I've got some trouble with my phone.
The battery was empty I plugged it with the official charger, I heard some crackling. Then it's hard to boot into bootloader, it wo'nt charge.
When I plug it it show the "charging icon" with 0% but without the green progression bar.
I can't relock the bootloader to flash a stock firmware. I'm S-ON.
You can see below my "fastboot getvar all" it's pretty empty so weird :
e_Kit_v1.0\Data>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA66TBNXXXX
all:
Click to expand...
Click to collapse
Anyone can help me ?
Thanks

That's the way the fastboot getvar all info is gonna look if you're in bootloader. It'll show when you're in download mode.

OK but I can't enter download mode.
I try to flash the *.img directly into bootloader but only hosd_signed.img work but I'm still at the same point.

GaTeRy86 said:
OK but I can't enter download mode.
I try to flash the *.img directly into bootloader but only hosd_signed.img work but I'm still at the same point.
Click to expand...
Click to collapse
If you're in bootloader mode you should be able to boot to download mode from there. It's the third entry from the top. Just navigate to it with the Vol- and confirm with the power button. If there post the getvar all without IMEI and serial number.
And please elaborate a little bit more which image are you trying to flash? Is the only problem that your device doesn't seem to charge or are there more problems you encounter. Did you previously flash a custom recovery or ROM?
Sent from my htc_pmeuhl using XDA Labs

I can't enter into download mode. The screen goes dark and the computer sees the device with "fastboot devices" but no other command works.
I had TWRP and last Venom rom on it. Everything was working fine.
I tried to flash every single img file in the firmware.zip from the last official release.
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Click to expand...
Click to collapse
I read that for some people that fix the problem.
It won't charge and it's also hard to enter bootloader, It goes often directly to black screen with htc written on it.

OK what if you try to boot into download mode even though the screen stays black. After issuing the command fastboot devices, to make sure it is properly recognized and comes back with its serial number in cmd, you could either try to flash the firmware.zip twice using fastboot - as long as it is the proper ZIP for your device. Another possibility would be to flash it from SDCard using the 2PS6IMG.zip method.
Last and least, you could try to run all full official RUU, in case something else git messed up. I assume this is the case, and fear that your try to flash partitions manually maybe just got it worse.
Without the getvar all from download mode I can't help any further, as there aren't enough informations to do so.
Sent from my htc_pmeuhl using XDA Labs

5m4r7ph0n36uru said:
OK what if you try to boot into download mode even though the screen stays black. After issuing the command fastboot devices, to make sure it is properly recognized and comes back with its serial number in cmd, you could either try to flash the firmware.zip twice using fastboot - as long as it is the proper ZIP for your device. Another possibility would be to flash it from SDCard using the 2PS6IMG.zip method.
Last and least, you could try to run all full official RUU, in case something else git messed up. I assume this is the case, and fear that your try to flash partitions manually maybe just got it worse.
Without the getvar all from download mode I can't help any further, as there aren't enough informations to do so.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Thanks for your help,
I can't flash the firmware in downloadmod, the only command which works is fastboot devices.
Flash the entire rom with RUU don't work because I don't have 30% battery and the last solution with SD card don't work too.

GaTeRy86 said:
Thanks for your help,
I can't flash the firmware in downloadmod, the only command which works is fastboot devices.
Flash the entire rom with RUU don't work because I don't have 30% battery and the last solution with SD card don't work too.
Click to expand...
Click to collapse
Try fastboot oem rebootRUU then try flashing the firmware after

xunholyx said:
Try fastboot oem rebootRUU then try flashing the firmware after
Click to expand...
Click to collapse
The phone just reboot and stay at the beginning with the battery logo with the lightning and without charging

GaTeRy86 said:
The phone just reboot and stay at the beginning with the battery logo with the lightning and without charging
Click to expand...
Click to collapse
Sadly welcome to the club , my phone is s-off with exactly the same issue, it's almost two months as a paperweight
It seems that it is difficult to understand even for the most illustrious of this forum that theres is no way to enter to recovery, download mode, RUU mode or whatever other mode in which you can do something more than flashing img in the broken bootloader.
https://forum.xda-developers.com/htc-10/help/htc-10-brick-usa-mex-wall-t3574704

You can't brick it from S-ON. It's just not possible.

tabp0le said:
You can't brick it from S-ON. It's just not possible.
Click to expand...
Click to collapse
That's not true.
Two examples are disconnecting your phone from your PC in the middle of an RUU, or having your phone die or power off during an OTA update.
Those two examples don't apply here, but I'm just pointing out that it is in fact possible.
The OP mentioned that there was a "crackling" noise when he plugged his phone in. Could be a loose wire or connection (which could happen by dropping the phone onto a hard surface) that fried a part of the mother board. That may not be the case here, but it is another way to get a hard brick.
---------- Post added at 11:14 AM ---------- Previous post was at 11:03 AM ----------
GaTeRy86 said:
I can't enter into download mode. The screen goes dark and the computer sees the device with "fastboot devices" but no other command works.
I had TWRP and last Venom rom on it. Everything was working fine.
I tried to flash every single img file in the firmware.zip from the last official release.
Quote:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
I read that for some people that fix the problem.
It won't charge and it's also hard to enter bootloader, It goes often directly to black screen with htc written on it.
Click to expand...
Click to collapse
You shouldn't have flashed the aboot.img
https://forum.xda-developers.com/showpost.php?p=69856732&postcount=972

xunholyx said:
That's not true.
Two examples are disconnecting your phone from your PC in the middle of an RUU, or having your phone die or power off during an OTA update.
Those two examples don't apply here, but I'm just pointing out that it is in fact possible.
The OP mentioned that there was a "crackling" noise when he plugged his phone in. Could be a loose wire or connection (which could happen by dropping the phone onto a hard surface) that fried a part of the mother board. That may not be the case here, but it is another way to get a hard brick.
---------- Post added at 11:14 AM ---------- Previous post was at 11:03 AM ----------
You shouldn't have flashed the aboot.img
https://forum.xda-developers.com/showpost.php?p=69856732&postcount=972
Click to expand...
Click to collapse
Good point! You're absolutely right. I wasn't even thinking about that!

[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]

Flashing signed stock firmware:
You need:
Latest signed stock firmware:
Europe (RETEU):
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
India (RETIN):
https://mirrors-obs-2.lolinet.com/f...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
US (RETUS):
https://mirrors-obs-2.lolinet.com/f...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
All other firmwares and locations:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Also:
flashallO.bat:
https://drive.google.com/file/d/1Ne7Kps25heUO7wsJ0Z4_X43eKQYRegoa/view?usp=sharing
Motorola drivers (Device Manager - former LMSA):
Motorola Device Manager
Motorola Device Manager, free download for Windows. Program to transfer data between Motorola devices and computers, update software and backup files.
motorola-device-manager.en.lo4d.com
Tiny ADB & Fastboot v1.4.0 signed;
Tiny_ADB_&_Fastboot_v1.4.0-signed.exe | Tool by K3V1991 for Misc. Software & Hardware Resources
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
1) Download the 8.1.0_OPS28.85-17-6-2 firmware for your region (it's the last one for the Moto G5+ (potter), there won't be any updates anymore, so no risk of bootloader downgrading)
2) Install Tiny ADB & Fastboot (best place is the root directory of C: or wherever your OS resides).
3) Extract the firmware to that ADB & Fastboot folder.
4) Download my "flashallO.bat" and move it to that folder too.It removes the need for you to manually flash all partitions, just double-click it and it'll run all the commands for you.
5) Download and install Motorola device drivers.The program is called "Motorola Device Manager".
6) Reboot your phone to the bootloader. To do this, turn it off, then hold down the power and volume down buttons until you see a bugdroid undergoing open-heart surgery.
7) Connect the phone to your PC with your USB cable. Type
Code:
fastboot devices
to check if your device is connected. A serial number should be shown.
8) Run the flashallO.bat script. (Caution: This will wipe your device completely!) It will take some time to flash, just be patient and don't worry.
If the command window appears for a brief moment and then disappears, the device drivers may not be installed correctly. You can ask me in that case, there are some special drivers that may solve that.
9) Once the command window closes, it should have completed the flashing process and you are safe to press the power key on the phone to start Android. Just make sure that the text near the buttons reads "START".
That's it.
You can save your (internal) data when you open the flashallO.bat and delete the command
Code:
fastboot erase userdata
so that it will be omitted.
I won't recommend it but it's possible.
Rooting:
You need:
Magisk 24.1:
https://github.com/topjohnwu/Magisk/releases/download/v24.1/Magisk-v24.1.apk
If you have problems with the newer Magisk builds (since v24) you may try
Magisk 23:
https://github.com/topjohnwu/Magisk/releases/tag/v23.0
or
Magisk 20.4: https://github.com/topjohnwu/Magisk/releases/tag/v20.4
TWRP 3.5.2_9-0:
https://eu.dl.twrp.me/potter/twrp-3.5.2_9-0-potter.img
Maybe you'll need:
Disable_Dm-Verity_ForceEncrypt.zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
- Download TWRP from the above link and place it in your ADB & Fastboot folder.
- Download magisk.zip (and Magisk Manager APK if you use version 20.4) and place it in your internal storage.
- Turn the phone off again and reboot to bootloader using previously mentioned key combination.
- Navigate to the folder where you placed the TWRP image.
- Hold down the "shift" key and right-click anywhere in the Explorer window,it should give you an option to "Open command window here."
- Now input the command:
Code:
fastboot flash recovery [filename].img
, where [filename] is the name of your TWRP image file. Tap Enter and it will take a few seconds to flash the new recovery.
- Alternatively, you can use "fastboot boot [filename].img" to temporarily boot TWRP for the purpose of flashing Magisk. This retains the stock recovery.
- Now that TWRP has been flashed, press the volume down key until you see the label on the side change to read "RECOVERY." At that point you can press the power button and you will boot right into TWRP.
- If you decide to decrypt your device:
In that case go to "Wipe" in TWRP and use "format data" (the option where you have to confirm with "yes"). Just wipe data is not enough!
- If you want your device to stay encrypted skip that step.
- Now press the "Install' button in TWRP and navigate to the location where the magisk.zip is located. Simply tap it and "Swipe to install."
- If you decided to decrypt your device normally magisk should take care that it doesn't get encrypted again.
Magisk only disables the enforced encryption flag, the device will still be encrypted and that's why a wipe of data is necessary to remove the encryption.
If that's not the case and you get problems to reboot flash Disable_Dm-Verity_ForceEncrypt.zip after magisk.zip.
More information about decryption/encryption:
https://didgeridoohan.com/magisk/Magisk#hn_Disabling_dm-verity_and_forced_encryption
- Reboot your device, if the Magisk Manager isn't installed already (it should) install the Magisk Manager APK.
Thanks to @Jrhotrod for parts of the rooting tutorial.
Edit: Updated Links again.(1-2022)

My 3 year old Moto G5 Plus running android 8 suddenly restarted a few days ago and went into Start up failure. It no longer shows My product or IMEI number. It just shows potter 000000000000000 32GB P3B
Bootloader logs read " Start up failure. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant" written in red.
I have my IMEI and product numbers saved on my pc in a notepad file, but the LMSA software does not recognise my device to even try to rescue it. I want to retrieve files from my phone before attempting a factory reset.
On using the LMSA, it says "lmsa doesn't match appropriate firmware. you can try to select a firmware manually" but then it has no option to select anything manually. I have my phone previously registered on the software on my PC.
I have not rooted my phone, nor used anything other than stock android. My bootloader is locked. I cannot remember if I had Developer options selected or not, most probably not.
On trying to go to recovery mode it says the same message " Start up failure. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant"
When I connect the phone to the computer, it recognises it (I hear a notification sound) and under Devices it shows under Unrecognised as "Fastboot potter s"
I've never flashed my phone but would it be possible to recover the files in the internal storage of the phone by installing TWRP (in a non rooted, bootloader locked phone) without data loss?
How does it work?
Please help! I really need to recover my photos and notepad notes. Is there any way? Any software?
Is there any way to flash stock ROM without losing data? I haven't attempted anything in the off chance that there is a way to recover internal storage data. It's absolutely essential to me. I don't care about the phone, I'm gonna replace it anyway.
If I can even switch on the phone for long enough to backup data from the phone, it will be enough.
I read in another thread that downgrading a Moto with a locked bootloader will hard brick the device. This thread. My bootloader/oem is locked. I've attached a screenshot from when I once connected my phone to LMSA a few weeks before it crashed, it showed my current version I was running at the time. I never got around to taking a backup of the phone, then.
These are the screens I get. I try to charge the phone in fastboot every day to keep it from dying completely.
I'm desperate.

Also Lolinet seems to be down. I tried to download RETIN firmware from the link you provided, but I only get
404 Not Found
nginx
What to do now?
I downloaded the firmware from Motorola Stock Room. Will that do?

I downloaded the firmware from Motorola Stock Room. Will that do?
[/QUOTE]
DwightKBrute said:
Also Lolinet seems to be down. I tried to download RETIN firmware from the link you provided, but I only get
404 Not Found
nginx
What to do now?
I downloaded the firmware from Motorola Stock Room. Will that do?
Click to expand...
Click to collapse
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: No way to save your data from an unroofed device with locked bootloader, I'm sorry.
You can omit the "fastboot erase userdata" command (see above thread) to save your internal storage when flashing the firmware but as you have problems with your device a complete clean start may be the only solution. But you can give it a try.

Wolfcity said:
I downloaded the firmware from Motorola Stock Room. Will that do?
Click to expand...
Click to collapse
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
View attachment 5162915
[/QUOTE]
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.

Also since I'm missing my IMEI and SKU, should I keep the erase modemst1 and fastboot erase modemst2 commands in the file?

DwightKBrute said:
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
View attachment 5162915
Click to expand...
Click to collapse
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
View attachment 5162925
View attachment 5162923
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
View attachment 5162927
[/QUOTE]
Copy this content and put it into a notepad:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Delete the fastboot erase userdata line and save it as .bat file (if your notepad has no option to save it as .bat save it as .txt and change the ending from .txt to .bat by hand).
And deactivate your Windows Defender when doing that and also when using the .bat file.

Wolfcity said:
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
View attachment 5162925
View attachment 5162923
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
View attachment 5162927
Click to expand...
Click to collapse
Copy this content and put it into a notepad:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Delete the fastboot erase userdata line and save it as .bat file (if your notepad has no option to save it as .bat save it as .txt and change the ending from .txt to .bat by hand).
And deactivate your Windows Defender when doing that and also when using the .bat file.
[/QUOTE]
So let me just recheck the steps.
1. Downloaded the firmware from Motorola Stock Room
2. Downloaded and installed Mini Adb.
3. Extracted the firmware to the same folder as the mini adb
4. Deleted the .bat file already present in the extracted firmware folder from MSR. Replaced that with the .bat file you have provided.
5. Erase userdata command removed.
6. Run the .bat file.
7. Wait for flashing to complete
Yes?

DwightKBrute said:
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
View attachment 5162915
Click to expand...
Click to collapse
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
View attachment 5162925
View attachment 5162923
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
View attachment 5162927
[/QUOTE]
Download (or copy) my flashallO.bat file delete,the erase userdata line
DwightKBrute said:
Copy this content and put it into a notepad:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Delete the fastboot erase userdata line and save it as .bat file (if your notepad has no option to save it as .bat save it as .txt and change the ending from .txt to .bat by hand).
And deactivate your Windows Defender when doing that and also when using the .bat file.
Click to expand...
Click to collapse
So let me just recheck the steps.
1. Downloaded the firmware from Motorola Stock Room
2. Downloaded and installed Mini Adb.
3. Extracted the firmware to the same folder as the mini adb
4. Deleted the .bat file already present in the extracted firmware folder from MSR. Replaced that with the .bat file you have provided.
5. Erase userdata command removed.
6. Run the .bat file.
7. Wait for flashing to complete
Yes?
[/QUOTE]
Sounds ok. The bat file has to be copied into the ADB & Fastboot folder (mini ADB) too.
Deactivate Defender and start the bat file.
Be patient.
And collect as many data from the flashing process as possible (screenshots etc.)

Well. I wasn't able to get many screenshots, it happened too quickly. But the phone is still stuck on fastboot, but this time the fastboot reason is given as: Last time flashing failed.
Oh well. I'll try again without removing the flashboot erase userdata?
failed to validate recovery image

DwightKBrute said:
Well. I wasn't able to get many screenshots, it happened too quickly. But the phone is still stuck on fastboot, but this time the fastboot reason is given as: Last time flashing failed.
Oh well. I'll try again without removing the flashboot erase userdata?
failed to validate recovery image
Click to expand...
Click to collapse
Seems your device has problems to erase partitions before flashing new stuff to them. Maybe search for blankflash files.

Where to find the blankflash file?

DwightKBrute said:
Where to find the blankflash file?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/potter/

Hello. I have a rooted Moto G5 Plus (Magisk) and I have also installed a Custom ROM with TWRP. I want to unroot the device and return it to absolute stock. Will this guide work in that case? If no, can anyone direct me to the correct guide?

DEJAVU54 said:
Hello. I have a rooted Moto G5 Plus (Magisk) and I have also installed a Custom ROM with TWRP. I want to unroot the device and return it to absolute stock. Will this guide work in that case? If no, can anyone direct me to the correct guide?
Click to expand...
Click to collapse
The above guide https://forum.xda-developers.com/t/guide-moto-g5-plus-flashing-stock-firmware-rooting-2021.4205293/ should be helpful for you. Flashing the latest signed stock firmware as described in the first part will take you to absolute stock.
A few points to take care of:
- Make sure that you chose the correct firmware for your location.
- Don´t delete the fastboot erase userdata command from the flashallO.bat so that it will be omitted because some parts of Magisk or other root apps may reside at that location.
- You have to erase everything to be on the safe side.
- So save your internal userdata like pictures, documents, music etc. to a PC or a SD card before you start the
process!
- Flashing stock will overwrite the recovery.img (TWRP) and the boot.img (Magisk) so you don´t have to unroot or reflash stock recovery.
If you want to relock your bootloader too (remember that you won´t get to the "nerver unlocked" state again, the device will flag the bootloader as "has been unlocked" even when you lock it):
-After flashing stock firmware open a command prompt in the ADB & Fastboot folder again and give the following commands one by one or use the attached relockO.bat file. the same way you did it with the flashallO.bat:
relockO.bat:
relockO.bat
drive.google.com
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 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 boot boot.img
fastboot oem lock
You can do that anytime, it hasn´t to be right after the firmware flash.

I flashed the ROM today and everything went well, except the IMEI is 0 and I cannot use VoLTE. What can I do?

DEJAVU54 said:
I flashed the ROM today and everything went well, except the IMEI is 0 and I cannot use VoLTE. What can I do?
Click to expand...
Click to collapse
What does getvar all say?
post it here after you remove imei line.
Code:
fastboot getvar all

sd_shadow said:
What does getvar all say?
post it here after you remove imei line.
Code:
fastboot getvar all
Click to expand...
Click to collapse
(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: ZY2244FVLG
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 10E5EE5600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(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: "Thu Aug 30 2:39:28 UTC 1973"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:8.1.0/O
(bootloader) ro.build.fingerprint[1]: PSS28.85-13-3/72e4:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.201.4.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_41.50.07.82u POTTER_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g70fa69f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Oct 10 11:58:58 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=26cc248-dirty
(bootloader) devcfg.git: git=26cc248-dirty
(bootloader) keymaster.git: git=26cc248-dirty
(bootloader) cmnlib.git: git=26cc248-dirty
(bootloader) cmnlib64.git: git=26cc248-dirty
(bootloader) prov.git: git=26cc248-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.062s

DEJAVU54 said:
I flashed the ROM today and everything went well, except the IMEI is 0 and I cannot use VoLTE. What can I do?
Click to expand...
Click to collapse
Have you ever flashed someone else's persist file?

Wolfcity said:
Have you ever flashed someone else's persist file?
Click to expand...
Click to collapse
No I have not. Only the PixelExp zip and now, the stock rom.
Anyways, after panicking a bit yesterday, I flashed the custom rom again and my IMEI and LTE returned, but I cannot place/receive calls. What can be done if I wanted to stay on the ROM but gain calling capabilities?
EDIT: I'd prefer to have everything working on the stock ROM if possible.