yashsingh1/xdaforums huggingface dataset:
[Moto E5 Guides, News, & Discussion] kiomet:
I have a problem, getvar says:

(bootloader) version: 0.5

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

(bootloader) product: nora

(bootloader) board: nora

(bootloader) secure: yes

(bootloader) hwrev: P4

(bootloader) radio: 7

(bootloader) storage-type: emmc

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

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

(bootloader) cpu: MSM8917

(bootloader) serialno: 73e064d

(bootloader) cid: 0xDEAD

(bootloader) channelid: 0x00

(bootloader) uid: D05BB0BD00000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: n/a

(bootloader) max-download-size: 535822336

(bootloader) reason: Last time flashing failed

(bootloader) imei: 000000000000000

(bootloader) meid:

(bootloader) date: 01-01-1970

(bootloader) sku: 000000000000000

(bootloader) carrier_sku:

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint:

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.full:

(bootloader) ro.build.version.qcom:

(bootloader) version-baseband:

(bootloader) kernel.version:

(bootloader) sbl1.git: sbl1.git

(bootloader) rpm.git: rpm.git

(bootloader) tz.git: tz.git

(bootloader) devcfg.git: devcfg.git

(bootloader) keymaster.git: keymaster.git

(bootloader) cmnlib.git: cmnlib.git

(bootloader) cmnlib64.git: cmnlib64.git

(bootloader) prov.git: prov.git

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

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

(bootloader) ro.carrier:

(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.105s
[Moto E5 Guides, News, & Discussion] sd_shadow:
I suggest trying boot into EDL

Is my device in EDL Mode?

How to boot into EDL Mode

Then use the blank-flash.bat

https://mirrors.lolinet.com/firmware/moto/nora/blankflash/
[Moto E5 Guides, News, & Discussion] kiomet:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem blankflash

...

(bootloader) command restricted

FAILED (remote failure)

finished. total time: 0.004s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot rrr.img

downloading 'boot.img'...

OKAY [ 0.589s]

booting...

(bootloader) permission denied!

FAILED (remote failure)

finished. total time: 0.593s

This is what happens when I try to do the methods explained in the links you gave me

Any ideas?
[Moto E5 Guides, News, & Discussion] sd_shadow:
What's the rrr.img?
[Moto E5 Guides, News, & Discussion] kiomet:
Recovery TWRP https://twrp.me/motorola/motorolamotoe5.html, i change the name to write it faster just that
[Moto E5 Guides, News, & Discussion] kiomet:
Any ideas?
[Moto E5 Guides, News, & Discussion] sd_shadow:
Sorry, I don't have other ideas.
[Moto E5 Guides, News, & Discussion] lucasymax:
file does not exist in mega Could you help me find it and download it?

thanks in advance
[Moto E5 Guides, News, & Discussion] zendude:
I have the Comcast version of Moto E5 Play james XT1921-1. The link to the stock firmware mentioned in the original post (https://mirrors.lolinet.com/firmware/moto/james/official/) shows AMZ, ATT, CCAWS, Cricket, Metropcs, RETUS, Sprint, and TMO. Which version would be compatible to a Comcast phone?

Below are the system info in the settings menu.

Android version: 8.0.0

Android security patch level: July 1, 2019

Baseband version: M8917_31.39.05.93Z JAMES_NA_CUST

Kernel version: 3.18.71-perf-g8f9e7c3 hudsoncm@ilclbld67 #1 Mon Jul 15 00:50:11 CDT 2019

Build number: OPPS27.91-157-9-2

Thank you.
[Moto E5 Guides, News, & Discussion] GOOGLE_USER:
Greetings, @zendude.

I wouldn't advise you to use any of those offerings, as they do not appear to match your device - though they may be compatible, I do not know. What I do know is that Comcast/Xfinity was, and may still be, an MVNO of Verizon. Therefore, I would expect the stock firmware to be tagged VZW, if not some variation of Comcast/Xfinity. Neither here nor there, I believe that I have good news for your situation. Do read on.

I have two of these devices, both rooted and Magisk'd up, though they have been sitting idle for some time. They are still running the stock ROM. Charged them both to 85% and stored away. Woke them up after seeing your post to check the details and batteries are still at 85%. I powered them up every six months, or so, to contemplate their usage possibilities only to realize that I do not have the time nor the drive that I used to have a couple of years ago in regards to device experimentations. At those times, I would recharge to 85% and store them again. This time they will be going on Ebay, listed as "Like New" and each with a bumper case, equally pristine. So, if this was beginning to sound like a sales pitch... well, wink - wink & nod - nod... it is not directed at you specifically, zendude, rather any passers-by who may have interest. Device sales via XDA are not allowed, so PM me and I'll provide additional information regarding my eBay listings. I hope that is allowed.

@Moderators - If it is not, please be merciful and consider my past contributions here on XDA. :unsure: :oops:😁

EDIT - I was joking here but should have been more thorough in my understanding of the rules.

None of the above stricken text is allowed to facilitate a device sale - or any type of sale, really.

I was wrong to have posted on the topic of an item for sale.

Anyway, of interest to you, zendude, may be the fact that I still possess the final and unmolested stock ROM that was applied to these devices with the rendered results - mimicking the information you provided - being the following for both devices:

Android version: 8.0.0

Android security patch level: May 1, 2020

Baseband version: M8917_35.45.05.99R JAMES_NA_CUST

Kernel version: 3.18.71-perf-g39378b1018d0 hudsoncm@ilclbld67 #1 Tue Apr 28 13:47:07 CDT 2020

Build number: OPPS27.91-157-9-15

I cannot recall exactly where I sourced the ROM, but I do not apply questionable software to devices ; at least no more questionable than what one can reasonably investigate. Point being, I choose sources with due caution for my devices and would treat yours no differently. If it was suspect then I wouldn't be offering it to you. If interested, reply here in-thread. Suggest MEGA or GOOGLE DRIVE to facilitate the transfer and I will attempt to upload and confirm within a few days time.

I can provide the file name of [RJAMES_OPP27.98_cid50_XT1921-1-SS_8.0.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip] which I would not have altered, if this will provide you with any sense of validity.
[Moto E5 Guides, News, & Discussion] zendude:
I have a moto g7 power also and kept a e5 play as a backup or an experimental device so I don't have much use for another phone but the file name you provided gave me a good clue as to what to look for. Thank you for the information.

Update: The comcast stock roms for moto e5 play XT1921-1 are at https://mirrors.lolinet.com/firmware/moto/rjames/official/Comcast.
[Moto E5 Guides, News, & Discussion] GOOGLE_USER:
First of all, you are welcome and glad I could offer some useful information.

Secondly, I wanted to highlight the above quote for the Comcast "RJAMES" variant users.

Ah, also, nice catch on your part. I looked at the tree, saw "james" under "moto" and scrolled to the "...60 more subfolders" and either blacked out or just gave up.

Either way, same result, no dessert for me.

Good lucks in your experimenting!
[Moto E5 Guides, News, & Discussion] Knightrider_kit:
So recently while using my phone to video chat the battery was not charging well cause my charger sucks so it kept saying charging usb and then it died. When I tried rebooting it keeps going straight to fastboot saying hab image not verified and boot image not verified. It seems to me that just flashing boot.img should fix it but I cannot find an image with the exact fingerprint. My finger print is:

ro.build.fingerprint[1]: .0/ODPS27.91-121-16-14/16:user/rel

I believe the correct image for this is:

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors.lolinet.com

Can I use this? And is my thinking correct in just flashing the boot.img or do I have to flash all the partitions?
[Moto E5 Guides, News, & Discussion] carlosuh:
Is it possible to boot this phone from an sd card? With locked bootloader and no recovery?

I was able to put my phone on QDL mode via test point but the blankflash throws the error "XML (0 bytes) not validated"

Did you manage to fix it? Im having the exact same problem but flashing the partitions didnt work for me.
[Moto E5 Guides, News, & Discussion] Knightrider_kit:
Yes it worked and all I did was what I thought the solution was, flash just the boot partition. Sorry I couldn't be more help.
[Moto E5 Guides, News, & Discussion] Cinephile 74:
Unfortunately, the download link to your Google Drive no longer exists, according to Google. Is there any possibility of providing a valid link or, can I get permission to view the page?

Thanks for your time
[Moto E5 Guides, News, & Discussion] sd_shadow:
These do not work?

https://mirrors-obs-2.lolinet.com/firmware/lenomola/2018/james/official/Cricket/

https://xdaforums.com/t/rescue-and-smart-assistant-lmsa.3951714/

https://t.me/s/MotoUpdatesTracker?q=xt1921-2

https://xdaforums.com/t/index-motorola-stock-firmware.4222605/
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
Why on earth would you want to relock the bootloader. Are you trying to unvoid your warranty? Relocking the bootloader is not necessary for installing OTA updates -- on Motorola devices anyway.
[Moto E5 Guides, News, & Discussion] amn92:
XT1944-3 Firmware

[MENTION=7383447]MotoJunkie01[/MENTION]: The firmware provided for XT1944-3 has issues with the touch screen. The notification bar from top keeps coming down and the random touches are done on the screen. Do we have any fix for this?
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
The firmware package is a leak from Motorola Mobility, so any bugs or instabilities are internal. I don't own the xt1944-3 so I'm not able to provide any bug fixes for reported issues.
[Moto E5 Guides, News, & Discussion] amn92:
Oh, got it. Thanks for the .56 build which you have provided. The phone(XT 1944-3) when I purchased had come with a .25 build on it. Can you please update me whenever you get the .25 build so that I can get back to stock? Thanks a lot
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
I never know what builds I'll get or when. But I will update the thread as new builds become available on my end.
[Moto E5 Guides, News, & Discussion] tbirdguy:
ok I concede to being a noob dumbass whose been here for years, suckas im in fear,

someone help me out with:

1. rooting the -3 tmobile variant

2. installing the OTA without relocking, ive tried the cricket BL and no go... and phone keeps wanting to auto update

and restarting and generally being a pain in my ass

3. getting a custom rom to work (which would eliminate the other issues)

4. educating me or giving me the information on how the F--k to do s--t on these ****ING PHONES
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
Ah hell, don't beat yourself up. These newer Moto devices, in addition to this Oreo source code, has sort of changed the whole ballgame on things.

• Ok first, as to the xt1921-3 T-Mobile variant, I haven't had any dealings with it as of yet. But, it's safe to assume that since you inquired about the bootloader, your device is bootloader unlocked. On installing OTAs, you do not need to relock your bootloader on a Moto device to take an OTA, so long as your /boot, /recovery, /system, /vendor and /oem partitions are in an untouched stock state. This means that you can't so much as mount one of these partitions as R/W, or the OTA will return an error and cease the update.

• So, to root your device, I would recommend following [MENTION=5337314]CodyF86[/MENTION]'s root and TWRP thread on the xt1921-5 variant. The Moto E5 Play variants (except for the Cricket and Verizon variants, which are locked down) have pretty much the same bells and whistles configuration-wise. For example I just flashed my xt1921-5 with the stock ROM I compiled for the xt1921-1 retail variant. Worked flawlessly. In fact I'd be willing to wager it would work on your device as well.

• Before I get ahead of myself, please explain the steps you've taken in rooting, installing TWRP, etc., including the setbacks you've had and any obstacles you're up against currently. Again, don't beat yourself up. These Moto E5's have put me back in the Rooting 101 textbooks myself. But I'll be glad to help you. Thanks
[Moto E5 Guides, News, & Discussion] tbirdguy:
thanks for being so cool about all this LOL

I have no idea if they are still untouched, but I followed the instructions and got twrp installed and took a nandroid backup. but that was with TWRP flashed already (was a dumb move to not just boot it through fastboot)

but i believe /boot, /system, /vendor and /oem are all still good via the twrp backup

I've tried to flash the recovery in the guide, from the cricket variant I believe , and the OTA still errored out. and when I flashed the complete firmware from the guide i had no data, and sim wasnt recognized, I figured this was the difference between cdma and gsm firmware, and left it at that...

I am currently running RR with no root (even though the package system-180818-arm-aonly-gapps supposedly contains su, at least its not a NO-SU variant.) and the camera works but its dark as hell

I got the nav buttons working thanks to the post earlier from [MENTION=3198335]allenjthomsen[/MENTION]

so all i really want now is root, so i can clear these android go apps...

I've tried using the procedure in this thread

and cant boot that kernel or mount the /vendor partition to do anything
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
Gotcha. Thanks for the clarification. So let's concentrate on root. Since you have already flashed your recovery partition with the TWRP custom recovery, and you have installed RR, you should be able to achieve systemless root at this point by merely booting back into TWRP and flashing a Magisk root script. (v16.0 is the current stable release; v16.7 is the current beta release. Both work great). Have you tried flashing Magisk yet from TWRP? Installing Magisk will unpack, patch, repack and flash your current boot image to achieve systemless root, which will allow you to make the changes you want to /system, uninstall system apps, etc.
[Moto E5 Guides, News, & Discussion] tbirdguy:
doesnt work, get /vendor errors
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
Ok. So you need to disable force encryption. What errors are you getting when you try to mount /vendor and push the fstab.qcom file to your device?
[Moto E5 Guides, News, & Discussion] tbirdguy:
> adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor
mount: mounting /dev/block/platform/soc/7824900.sdhci/by-name/vendor on /vendor failed: No such file or directory

>adb push fstab.qcom /vendor/etc/fstab.qcom
fstab.qcom: 1 file pushed. 0.1 MB/s (1696 bytes in 0.032s)

then I flashed Magisk 16.0 and it doesnt boot... takes me to bootloader
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
It appears in the second example you listed that the qcom.fstab file did push to your /vendor partition. Once it is pushed, you need to reboot TWRP recovery, select Wipe, then select Format Data in the lower right of the screen. Doing this, of course, will erase all saved files and media on your device. But formatting /userdata is necessary to decrypt your device.
[Moto E5 Guides, News, & Discussion] tbirdguy:
Ok when the push takes it allows me to flash magisk 16.0, but doesnt boot... takes me to bootloader...

Tried 16.7 next... it booted and holy **** **** hot damn I GOT ROOT

THANKS SOFA KING MUCH!!!!

MotoJunkie01,

thanks for taking the time and dealing with all my ego bull**** in this... this **** is next level compared to this old ****... i mean i came from eclair, and putting froyo on the nexus one (cyanogenmod FTW) and black rose, the htc amaze where you had to physically bridge some **** on the board to get s-off, to an s3 to an m7, to a blu pure xl (that i ****ING LOVE, but died (mainboard, literally changed entire rest of phone, screen and digi, battery and daughterboard) and all kinda of other adventures has not prepared me for any of this...

so thank you sofa king much man, i appreciate all the time and help
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
Good deal. Ahh yes the old Froyo and Eclair ROMs. Way back in the day. Man things have sure changed these days. Glad you got it going. Root is a beautiful thing.
[Moto E5 Guides, News, & Discussion] tbirdguy:
Adaway and titanium backup.. no more loading all my apps and dealing with that...

you are THE MAN... thanks again for walking me through this... i think i had done all this before but never with the beta magisk and the old one doesn't boot...

Im about to cry (watching death of supaman) and i dunno if cause supes is dead or im so happy

edit - now im watching UP, and kevin bird is one of my favorite things ever, but the beginning of this movie is BRUTAL.. so def crying from the movies now lol
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
I'm happy that you're happy. It's all good. Any time friend.
[Moto E5 Guides, News, & Discussion] madbat99:
Can't wait for the next Superman animated movie after death of Superman. "Reign of the Supermen". With all the supes wannabes. Superboy, Steel, The cyborg, and the Eradicator.

[youtube]TmFTwQ4h8HU[/youtube]

Sorry for the OT [MENTION=7383447]MotoJunkie01[/MENTION] but I think I'm gonna grab one of these e5 play's. Virgin Mobile. My e4 is dying.
[Moto E5 Guides, News, & Discussion] tbirdguy:
e5 has been good phone for me, especially since I got RR and root...

i used to consider myself more of a super user, and dint think this phone would be enough got me... but it has been great so far...
[Moto E5 Guides, News, & Discussion] tbirdguy:
Errors I wasa getting were unable to mount vendor partitions, but since I was able to push fstab without mounting /vendor, I got it all working and have RR running with magisk, so all is good,

thanks for all the help man!
[Moto E5 Guides, News, & Discussion] MotoJunkie01:
That's great [MENTION=2360894]tbirdguy[/MENTION]. I'm always happy to hear a success story. Good work.
[Moto E5 Guides, News, & Discussion] tbirdguy:
DO you not remember helping me? LOL

the life of someone who helps so many people that the memories fall off in days lol

you are the man motojunkie, thanks for all the help again!
[Moto E5 Guides, News, & Discussion] amn92:
XT1944-5 Firmware

Hi [MENTION=7383447]MotoJunkie01[/MENTION], I am stuck in a bootloop for XT1944-5. Will you be having any firmware for this model? Thanks in advance

---------- Post added at 04:53 PM ---------- Previous post was at 04:53 PM ----------

Hi [MENTION=7383447]MotoJunkie01[/MENTION], I am stuck in a bootloop for XT1944-5. Will you be having any firmware for this model? Thanks in advance
[Moto E5 Guides, News, & Discussion] j256:
I flashed the files for my Moto e5 Play, and it will boot normally now. However, some functionality is lost. I can't turn on my wifi (button literally does nothing), can't toggle bluetooth on/off, etc. There was an error I believe during the flashing process, gpt.bin failed with preflash validation and another one. Could that be the cause? What do I do?

Initially, I installed the TWRP for the device and then flashed the no-verity kernel and was stuck in a boot loop. Messed around a little bit then it would only stay on the screen with the Moto M and "powered by android".

Please help me.
[Moto E5 Guides, News, & Discussion] madbat99:
Sounds like you use a boot image from an older firmware. That can bork wi-fi and Bluetooth on many devices
[Moto E5 Guides, News, & Discussion] j256:
The one in OP was the only boot image I could find of the stock ROM. Unless there's a newer, recent one I don't know what to do.
[Moto E5 Guides, News, & Discussion] madbat99:
Downgrade the rest of the firmware (the sameone as the boot.img you used). But not bootloader or gpt.bin.
[Moto E5 Guides, News, & Discussion] j256:
Could you explain the process, hopefully step-by-step? I know little to none about doing all of this and the only stuff I know is from messing up this phone and trying to repair it.
[Moto E5 Guides, News, & Discussion] madbat99:
It's in the op of this thread
[Moto E5 Guides, News, & Discussion] j256:
The thing at the bottom? That's what I did in the first place and have the wifi/bluetooth problems.
[Moto E5 Guides, News, & Discussion] madbat99:
Looks like

Instructions say:

WARNING: These stock Android 8.0.0 firmware packages should not be used in an attempt to downgrade your device to an earlier firmware build. (While downgrading is possible, only the more advanced users should attempt it ) Use this firmware & guide only if your device has never been upgraded beyond the build number of the firmware package in the download link. Attempting to downgrade your partition index (gpt.bin) or your bootloader partitions (bootloader.img) can result in a hard-bricked device -- and typically bricked beyond repair. By proceeding further, you are assuming sole responsibility for the integrity and functionality of your device, thus absolving me from any civil liability in the event of bricked or otherwise inoperable devices.

1. Download your firmware package from the link above 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 boot boot.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 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

Upon reboot, your device should be fully restored to its stock factory configuration and, as such, will be fully capable of installing any future OTA update packages.

Taken from op.

If you don't have a firmware to match the boot.img, I flash the firmware. Do what you like, at your risk.
[Moto E5 Guides, News, & Discussion] j256:
Those are the set of instructions I followed. I'm just going to wait until the firmware for my specific model (XT1921-3) ends up getting released here and use my crappy 5S that can't take calls in the meantime.
[Moto E5 Guides, News, & Discussion] madbat99:
Oh, I didn't realize you were using the wrong firmware for your device.
[Moto E5 Guides, News, & Discussion] Starkiller2:
So since I turned my e5 into a tablet somehow, I replaced it with a g6 play. I just couldn't get it to work, even with all your help. Thanks again for trying so hard [MENTION=7383447]MotoJunkie01[/MENTION]

Anyway, lesson learned, took backups of everything but the box it came in this time. lol. You're awesome. Start wearing a cape.