yashsingh1/xdaforums huggingface dataset:
[Moto E5 Guides, News, & Discussion] bubba1601:
You are inputting wrong commands in fastboot.

Fastboot flash recovery boot.IMG is not correct.

The correct command is fastboot flash boot boot.img

Or

Fastboot flash OEM OEM.img

Or

Fastboot flash vendor vendor.img

You also tried the "retail EU" firmware

That's for sim unlocked variants of the E5 play only, if your device is locked to Tesco you should only use the Tesco firmware.

Go back to the first post, and read the flashing instructions again.

Look at my screenshot.

It won't work unless you follow the instructions each line in the correct command in the correct order

Please take time to read it properly and fully before trying again.
[Moto E5 Guides, News, & Discussion] bubba1601:
Are you sure it's a XT1920-15?

Are you sure it was on Tesco?

What network was it before you unlocked it?

I have to ask these questions because I don't think you know what you are doing or have been doing with the device.

You flashed two different firmwares before and could have seriously damaged the device.

Both the firmwares you quoted in your comments do flash successfully on my 1920-15.

My own 1920-15 has RETAIL_GB firmware.

I tried the Tesco one after soft bricking my device a couple of weeks ago.

It does flash but doesn't allow me to use my Smarty (Three UK) SIM card, so the firmwares you tried do actually work on 1920-15.

You either don't have a 1920-15, you are not flashing the correct firmware for the device you have or the sigma /flashing process you did has damaged your device.

Im NOT being mean here, but it's important to warn everyone not to attempt these things without knowing what they are doing or researching and reading about what they are doing before attempting anything and asking for help of they are unsure - you unfortunately did not even read the flashing commands correctly AND flashed TWO different firmware!
[Moto E5 Guides, News, & Discussion] daddyunlocker:
Sir its 100% on tesco and i did write 3 times with tesco firmware but problem was same so i try to write other firmwares . phone is 100% on tesco i did use tesco sim before unlock. if commands are incorrect so please send here commands and is it possible to alive this device via custom firmware or via any other way?
[Moto E5 Guides, News, & Discussion] bubba1601:
Ok, but you have not explained why you "unlocked" the device with sigma and the process involved?

I think sigma has caused your device problem.

I sent you a screenshot of the full commands on the previous page of this thread.

There's no problems with the Tesco firmware, it flashes with no issues.

So it's working out what sigma has done to your device or what your are doing wrong while trying to reflash stock.

And to answer your other question, you cannot "alive" your device without flashing stock first, GSIs (custom ROMs) need stock or stock + Lineage 15.1 to work properly.
[Moto E5 Guides, News, & Discussion] daddyunlocker:
I have shop and customer did come for unlock his phone to use another network sim in his phone. Phone was working on tesco before unlock after unlock it was showing signal of other network but show error on screen ( com.motorola.has.stopped ) etc then i try to flash tesco firmware. Flash was successfully write done but problem did still there then someone give me other firmware links for try and now phone in fastboot . I am sending you picture check and tell me how i can write again tesco firmware on this phone.
[Moto E5 Guides, News, & Discussion] bubba1601:
[MENTION=9611623]daddyunlocker[/MENTION]

******* XT1920 ******

Moto E5 Play (PettyL) Android Go Edition

Android Version: 8.1.0 (Android Go)

Build No. OPGS28.54-19-2

Radio Version: M8917_20.23.05.64R

System Version: 28.201.2.pettyl.retail.en.US

Security Patch Level: Oct 9, 2018

Package Size: 975.9 MB

Note: This firmware package is for the Android Go Edition of the Moto E5 Play only. This package is much more lightweight in size in contrast to the Android 8.0.0 packages for other Moto E5 Play models. It also has seven system.img_sparsechunks, whereas the standard Android 8.0.0 packages for the E5 Play have either four or five system files. To install this package, be certain to flash all system.img_sparsechunk files, and not just the four listed in the below instructions. So, add these lines, in the proper numerical sequence:

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

1. Download your firmware package and extract the contents of the archive to your adb/fastboot directory on your PC;

2. Boot your device into AP Fastboot Mode by first powering down your device and then simultaneously holding the Power + Volume Down keys for around 8 seconds, until you see AP Fastboot Mode on your device display;

3. Connect your device to your PC using the OEM supplied or quality-equivalent micro USB to USB syncing cable;

4. Open a command window in the path of your adb/fastboot directory;

5. Enter this command:

fastboot devices

Press Enter/Return

If your device and PC are properly connected, an alpha-numeric string will appear in the command window synonomous to your device serial number;

6. After ensuring a proper connection, execute the following commands:

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash dsp adspso.bin

fastboot flash bootloader bootloader.img

fastboot flash recovery recovery.img

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

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 erase DDR

fastboot erase cache

fastboot erase userdata

fastboot flash oem oem.img

fastboot flash vendor vendor.img

fastboot oem fb_mode_clear

7. Now reboot your device by entering:

fastboot reboot

Press Enter/Return

If this doesn't work I'm not sure what to suggest.

Goto the MOTO E5 thread on telegram and ask for help, I'm out of ideas

Sorry
[Moto E5 Guides, News, & Discussion] skullkid383:
If its windows pc I noticed that u have to do

./fastboot instead of just fastboot granted that common sense but dude obviously is new to flashing firmware

---------- Post added at 04:20 PM ---------- Previous post was at 03:56 PM ----------

secondly never flash another variants FW once you have the bootloader unlocked most of the time it let's u use other sim card with it on custom roms and flashing wrong FW can result in bricking the phone and it being as useful as a paper weight
[Moto E5 Guides, News, & Discussion] bubba1601:
You Just need to Type Fastboot on windows 10 using 15 second ADB from here on XDA.

Not had any issues flashing stock or GSIs to my E5 play and never had to type ./ Before fastboot.

I agree with you though, the OP has both unlocked his device with SIGMA and flashed two different firmwares, that's probably caused irripairable damage.
[Moto E5 Guides, News, & Discussion] skullkid383:
Weird my wife's windows 10 needed ./ And no idk y but I'm a Linux fan all day everyday don't know to much about winblows and hopefully he learns not to flash on other ppls phones after that and also reads more into stuff first cause I personally believe SIGMA broke something firmware wise and it's best to unlock it your self that way no third party is responsible for breaking something and u know what you did if something does go wrong you can fix it by flashing stock and do same steps minus the one that broke something.
[Moto E5 Guides, News, & Discussion] bubba1601:
Another peculiarity.

In the UK, Tesco sell the MOTO E5 Play for either

£7.50 per month with inclusive calls/text/data

Or

£99 locked to Tesco.

But

My E5 play is not locked to any network (SIM unlocked)

And cost £69.95 from Argos.

So why did someone pay £99 for his device then ask that guy to unlock it, when the SIM unlocked version is over £20 cheaper?

The whole thing doesn't make sense to me and seems a bit dodgy to be honest.
[Moto E5 Guides, News, & Discussion] skullkid383:
To be honest dude said someone bought a phone at his shop but wanted different service so most likely a mom and pop store and he either didn't have other variants or talked them in to buying the more expensive one to make more profit and thought it's same phone so I should be able to flash the other carriers FW so then I can sell it at a higher price but give them the same phone HOLY CRAP I just realized dude was flashing boot.img to recovery a cpl posts back WTH!! DUDE JUST NEEDS TO GIVE UP AT THAT POINT LMAO:eek:
[Moto E5 Guides, News, & Discussion] Chave3:
I accidentally tried to root my Moto E5 Play Go without realizing it was the Go version since there was no word "Go" in the box. I tried to restore but I run into some errors while putting in the commands.

C:\Users\Chave\Desktop\platform-toolsj>fastboot flash partition gpt.bin

Sending 'partition' (45 KB) OKAY [ 0.000s]

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: '')

Finished. Total time: 0.109s

C:\Users\Chave\Desktop\platform-toolsj>fastboot flash bootloader bootloader.img

Sending 'bootloader' (7483 KB) OKAY [ 0.250s]

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: '')

Finished. Total time: 0.500s

C:\Users\Chave\Desktop\platform-toolsj>fastboot flash recovery recovery.img

Sending 'recovery' (24576 KB) OKAY [ 0.805s]

Writing 'recovery' (bootloader) Image size exeeded partition limits

(bootloader) Preflash validation failed

FAILED (remote: '')

Finished. Total time: 0.868s

The phone's screen is completely black and only lights up when I boot into TWRP with the "fastboot boot" command, but it's still black.
[Moto E5 Guides, News, & Discussion] bubba1601:
Device version?

Using the correct firmware for that device?
[Moto E5 Guides, News, & Discussion] Chave3:
At first I flashed the wrong FW stock version but now I'm sure it's XT1920-18 TELMXLA since that's what it says on the box. Flashing the wrong FW once was bad enough but twice? Today was not my day
[Moto E5 Guides, News, & Discussion] Chave3:
Oh forgive me for being vague but what I meant was that even after trying to flash the correct firmware I still have this problem. Also one more thing, if the phone got a system update recently before the flashing would this prevent me from flashing a stock firmware from the internet that is older than said system update? Maybe this is the cause.
[Moto E5 Guides, News, & Discussion] bubba1601:
No, thats not right.

I just flashed stock firmware for my XT1920-15 PETTYL that was older than I was running.

It flashed fine then updated back to the newer version after set up.
[Moto E5 Guides, News, & Discussion] Chave3:
Oh I see. Well I'm stumped then. I'll post the getvar output just incase anyone can tell anything from it, cause I don't know what I'm looking for.

C:\Users\Chave\Desktop\platform-tools>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: moto-msm8917-BE.4F

(bootloader) product: pettyl

(bootloader) board: pettyl

(bootloader) secure: yes

(bootloader) hwrev: P3

(bootloader) radio: 2

(bootloader) storage-type: emmc

(bootloader) emmc: 16GB SAMSUNG FE62MB RV=08 PV=03 FV=0000000000000003

(bootloader) ram: 1GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F

(bootloader) cpu: MSM8917

(bootloader) serialno: ZY322ZTV2M

(bootloader) cid: 0x0032

(bootloader) channelid: 0x03

(bootloader) uid: 1BA5854E00000000000000000000

(bootloader) securestate: flashing_unlocked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 245366784

(bootloader) reason: Volume down key pressed

(bootloader) date: 08-15-2018

(bootloader) sku: XT1920-18

(bootloader) carrier_sku: XT1920-18

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint[0]: motorola/pettyl_amx/pettyl:8.1.0/O

(bootloader) ro.build.fingerprint[1]: PGS28.54-19-2/2bd1:user/release-ke

(bootloader) ro.build.fingerprint[2]: ys

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.full[0]: Blur_Version.28.201.2.pettyl_amx.

(bootloader) ro.build.version.full[1]: amx.en.US

(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0

(bootloader) version-baseband: M8917_20.23.05.64R PETTYL_LATAM_CUST

(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g081bc62 (hud

(bootloader) kernel.version[1]: soncm@ilclbld26) (gcc version 4.8 (GCC)

(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Oct 9 01:23:08 CDT

(bootloader) kernel.version[3]: 2018

(bootloader) sbl1.git: git=MBM-NG-VBE.4F-0-g8ffb6ee

(bootloader) rpm.git: git=02a0726-dirty

(bootloader) tz.git: git=MBM-NG-VBE.4F-1-g2fa01bd-dirty

(bootloader) devcfg.git: git=MBM-NG-VBE.4F-1-g2fa01bd-dirty

(bootloader) keymaster.git: git=MBM-NG-VBE.4F-1-g2fa01bd

(bootloader) cmnlib.git: git=MBM-NG-VBE.4F-1-g2fa01bd

(bootloader) cmnlib64.git: git=MBM-NG-VBE.4F-1-g2fa01bd

(bootloader) prov.git: git=MBM-NG-VBE.4F-1-g2fa01bd-dirty

(bootloader) aboot.git: git=MBM-NG-VBE.4F-0-g4e3d3ac

(bootloader) frp-state: no protection (0)

(bootloader) ro.carrier: amxmx

(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.154s

I just realized it's actually registering touches while booted to TWRP despite the black screen since it vibrates when I tap where the back button should be. I dunno if this can help in some way.
[Moto E5 Guides, News, & Discussion] bubba1601:
Boot to fastboot and type "fastboot -w"

Tell us what happens (it may take a while)
[Moto E5 Guides, News, & Discussion] Chave3:
Got this

C:\Users\Chave\Desktop\platform-tools>fastboot -w

Erase successful, but not automatically formatting.

File system type raw not supported.

Erase successful, but not automatically formatting.

File system type raw not supported.

Erase successful, but not automatically formatting.

File system type raw not supported.

Erasing 'userdata' OKAY [ 0.082s]

Erasing 'cache' OKAY [ 0.010s]

Erasing 'metadata' (bootloader) Permission denied

FAILED (remote: '')

Finished. Total time: 0.167s
[Moto E5 Guides, News, & Discussion] bubba1601:
Now flash stock
[Moto E5 Guides, News, & Discussion] Chave3:
I get the same errors as before with these 3 commands

C:\Users\Chave\Desktop\platform-tools>fastboot flash partition gpt.bin

Sending 'partition' (45 KB) OKAY [ 0.012s]

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: '')

Finished. Total time: 0.109s

C:\Users\Chave\Desktop\platform-tools>fastboot flash bootloader bootloader.img

Sending 'bootloader' (7483 KB) OKAY [ 0.382s]

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: '')

Finished. Total time: 0.596s

C:\Users\Chave\Desktop\platform-tools>fastboot flash recovery recovery.img

Sending 'recovery' (24576 KB) OKAY [ 1.194s]

Writing 'recovery' (bootloader) Image size exeeded partition limits

(bootloader) Preflash validation failed

FAILED (remote: '')

Finished. Total time: 1.266s
[Moto E5 Guides, News, & Discussion] weakNPCdotCom:
Sorry for the delay in updating firmware links guys. I will try to get the rest of the latest firmware online by this weekend.
[Moto E5 Guides, News, & Discussion] remarkablecow913:
Have you tried putting stock recovery back in but keep your magisk Root? That is what I had to do to get it out of same situation. Although I would have the na at the top

---------- Post added at 12:31 PM ---------- Previous post was at 12:25 PM ----------

On the post before this go edit your imei off your message. That could give a lot of personal information.
[Moto E5 Guides, News, & Discussion] bubba1601:
I found myself in the same situation a few days ago.

Fastboot -w then reflashed stock worked for me, but I'm using the PETTYL UK E5 play
[Moto E5 Guides, News, & Discussion] Chave3:
I didn't even get to the part where I put magisk, at some point it gave me some error and that's when I tried to reflash stock

fastboot -w still gives me a permission denied error.
[Moto E5 Guides, News, & Discussion] remarkablecow913:
I honestly am not sure then. I had to flash all the stock files separately in order to get back to normal. gpt.bin would not flash and something else. But it did make my phone work again. I just get the na at the top for a few seconds, and stock recovery. But I was able to root ok. My suggestion would be to go back to stock with fastboot
[Moto E5 Guides, News, & Discussion] LenovoTech:
When flashing a firmware package which is an earlier version than the most recent device version, it is completely normal for fastboot to reject gpt.bin & bootloader.img. This is a safety mechanism present in your /aboot (Application Bootloader) which prevents downgrading of the partition index table (gpt.bin) and the bootloader firmware (bootloader.img). In other words, if fastboot did not reject gpt.bin and bootloader.img, downgrading either of these entities would hard brick your device due to Motorola's notorious /sbl1 qFuse. Once gpt.bin and bootloader.img are upgraded to a newer version, you may rest assured there is no going back -- you may not un-ring the proverbial bell. This is in no way a negative thing -- it is merely the Motorola firmware protocol. The Motorola Memorial Cemetery is quite full of poor souls who have tried to downgrade these hard-knock partitions. I would love to have a dollar for every defective device we receive in the tech department -- on a warranty basis -- which has been hard bricked by an attempted downgrade to /sbl1. Once we see the qFuse log of the device, the warranty is of course null and void. Only EDL --via QPST/QFIL with firehose -- will revive the device. Per department protocol, we rarely J-Tag or otherwise rebuild the eMMC.

In sum, downgrading a Motorola device's firmware via fastboot is both safe and practical, per downgrade prevention mechanisms inherent to the bootloader firmware. Personally, when downgrading (or unsurre), I merely skip over gpt.bin & bootloader.img, since fastboot will reject these files anyway.
[Moto E5 Guides, News, & Discussion] remarkablecow913:
I forgot to ask. Why does the boot.img and recovery .I'm have a bad signature when flashing from fast boot? All the rest is perfect I even flashed got.bin and about by following the commands you included in the flashfile. But recovery and boot.img flashed ok but give bad signature

Thank you and your team by the way for the most current build I found. It was linked from here originally (I think) but I did a search and found on a different site a more current fw that was for a subsidy instead of plain t mobile. Which works but isn't correct for the phone. Same as the custom roms for this device.

---------- Post added at 06:04 PM ---------- Previous post was at 05:31 PM ----------

And one more question.. if the us variant doesn't have dual SIM and Moto put out so many of these different variants. Do you know why a dual SIM tray was included? It fits an sd card but also fits another Sim in the opposite direction
[Moto E5 Guides, News, & Discussion] LenovoTech:
As to your first question, anytime you flash your /boot or /recovery partition while the bootloader is in an unlocked state, you will get a key signature error, even if the firmware package is genuine and has been digitally signed by the OEM or provider. This is 100% normal and will not adversely affect the firmware installation or functionality of the Android OS. During boot, the "N/A" and "Bad Key" notifications are certainly annoying. These can be masked by flashing your /logo partition with a custom boot logo which had been crafted to hide the error notifications. If you need I can get you links to some attractive custom logos to hide the boot error nags.

To your other questions, I'll try and get you some info.

I have PM'd you a link to my team's Moto firmware repo. I'm a new member and cannot yet post links. Please share the link here. The repo has hundreds of builds for virtually every Moto smartphone ever made, including carrier specific and region specific builds. All free of charge as well.
[Moto E5 Guides, News, & Discussion] SOU55:
i followed the steps for the tmobile and i get bootloop
[Moto E5 Guides, News, & Discussion] LenovoTech:
Guys for anybody who needs it, this is a firmware repo for virtually every Moto smartphone ever released, including carrier, regional, retail & oem-specific builds.

https://mirrors.lolinet.com/firmware/moto/

These firmwares are all free of charge. However, for those members able, please consider a small donation by selecting the donate option near the top of the webpage. For members who can't afford it, that's okay too. I only ask because my team has worked ceaselessly over the course of several months to amass the hundreds of packages in this repo.
[Moto E5 Guides, News, & Discussion] remarkablecow913:
Sorry I linked that to the wrong posts. I just used the firmware that you provide on this link. Https://mirrors.lolinet.com

Thank you guys so much. It is even the most current October security patch. You guys rock.

So for any one not sure. Go to the linked page by Lenovo team and choose firmware/official/ then find Hannah and then your carrier. All are there for each major carrier. After download unzip the .XML file and look for the specific document flashfile.xml . You will enter your bootloader then begin with the line

Fastboot flash partition gpt.bin and then follow evwryline in order all the way to fastboot erase DRR

After you are done with flashing remove USB and just boot like normal. Everything is perfect. If you have unlocked bootloader it will still say bad key or na but no worries. It will boot just fine. Then you are free to mess up your beautiful phone once again.

PS. Can someone tell me how to get twrp to stick without boot loop!! Or so we have to fastboot boot twrp Everytime we want to use it?? It's driving me nuts
[Moto E5 Guides, News, & Discussion] LenovoTech:
Have you tried installing TWRP from TWRP? In other words, save a copy of the twrp.img on your device in internal or external storage. Boot into TWRP from fastboot. Select Install, then choose the Install Image option in the lower right, navigate to the saved location of twrp.img on your device, then choose Recovery from the partition options. Swipe the action bar to install it. Now Reboot Recovery and see if it sticks.