• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Help Thread][Moto E 5 / E5 Plus/Play/Cruise] Ask Any Question, Noob Friendly(2018)

Search This thread

joeyxl

Senior Member
Apr 29, 2008
413
35
Newmarket
hey all im having some issues.

i had linage OS on my moto e5 play james canadian variant. i decided to flash the stock rom on it again. after following the instructions on here, i was able to get it to boot up with the stock rom with no issues, but im having an issue with cellular, i have no service and it looks like it doesn't even recognize the cellular modem, i do get bluetooth and wifi though. Can anyone tell me what i did wrong and what i need to do to fix it? the model number is xt1921-1.
 

sd_shadow

Recognized Contributor
Sep 21, 2011
18,333
2
8,878
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
hey all im having some issues.

i had linage OS on my moto e5 play james canadian variant. i decided to flash the stock rom on it again. after following the instructions on here, i was able to get it to boot up with the stock rom with no issues, but im having an issue with cellular, i have no service and it looks like it doesn't even recognize the cellular modem, i do get bluetooth and wifi though. Can anyone tell me what i did wrong and what i need to do to fix it? the model number is xt1921-1.
What does getvar all say? Remove the imei before posting.
Code:
fastboot getvar all
 
  • Like
Reactions: faheyd

joeyxl

Senior Member
Apr 29, 2008
413
35
Newmarket
What does getvar all say? Remove the imei before posting.
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BE.4B
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(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: ZY323VM75K
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8f
(bootloader) uid: 2DDA057700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351839092569058
(bootloader) meid:
(bootloader) date: 04-12-2019
(bootloader) sku: XT1921-1
(bootloader) carrier_sku: XT1921-1
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 8:50:31 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/rjames_f/rjames_f:8.0.0/O
(bootloader) ro.build.fingerprint[1]: PP27.91-114/121:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.231.121.rjames.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gcb03f6a-0001
(bootloader) kernel.version[1]: 5-g7ae439e ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jul
(bootloader) kernel.version[3]: 31 10:38:19 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VBE.4B-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=MBM-NG-VBE.4B-0-g5fefee4-dirty
(bootloader) devcfg.git: git=MBM-NG-VBE.4B-0-g5fefee4-dirty
(bootloader) keymaster.git: git=MBM-NG-VBE.4B-0-g5fefee4
(bootloader) cmnlib.git: git=MBM-NG-VBE.4B-0-g5fefee4
(bootloader) cmnlib64.git: git=MBM-NG-VBE.4B-0-g5fefee4
(bootloader) prov.git: git=MBM-NG-VBE.4B-0-g5fefee4-dirty
(bootloader) aboot.git: git=MBM-NG-VBE.4B-0-g4e376e8
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: rcica
(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

for some reason the baseband is missing.
 

sd_shadow

Recognized Contributor
Sep 21, 2011
18,333
2
8,878
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BE.4B
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(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: ZY323VM75K
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8f
(bootloader) uid: 2DDA057700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351839092569058
(bootloader) meid:
(bootloader) date: 04-12-2019
(bootloader) sku: XT1921-1
(bootloader) carrier_sku: XT1921-1
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 8:50:31 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/rjames_f/rjames_f:8.0.0/O
(bootloader) ro.build.fingerprint[1]: PP27.91-114/121:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.231.121.rjames.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gcb03f6a-0001
(bootloader) kernel.version[1]: 5-g7ae439e ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jul
(bootloader) kernel.version[3]: 31 10:38:19 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VBE.4B-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=MBM-NG-VBE.4B-0-g5fefee4-dirty
(bootloader) devcfg.git: git=MBM-NG-VBE.4B-0-g5fefee4-dirty
(bootloader) keymaster.git: git=MBM-NG-VBE.4B-0-g5fefee4
(bootloader) cmnlib.git: git=MBM-NG-VBE.4B-0-g5fefee4
(bootloader) cmnlib64.git: git=MBM-NG-VBE.4B-0-g5fefee4
(bootloader) prov.git: git=MBM-NG-VBE.4B-0-g5fefee4-dirty
(bootloader) aboot.git: git=MBM-NG-VBE.4B-0-g4e376e8
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: rcica
(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

for some reason the baseband is missing.
Where did you get the firmware you flashed?
 

sd_shadow

Recognized Contributor
Sep 21, 2011
18,333
2
8,878
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
Getvar is showing several errors, I suspect you flashed the wrong firmware.
try this one
https://mirrors.lolinet.com/firmware/moto/rjames/official/RCICA/
XT1921-1_RJAMES_RCICA_8.0.0_OPPS27.91-157-12-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

 

andres0185

Member
Nov 8, 2020
8
1
some rom 9-10-11 for motoE (XT1920DL)
 

Attachments

  • Screenshot_20211119-214845 (2).png
    Screenshot_20211119-214845 (2).png
    41.9 KB · Views: 3

sd_shadow

Recognized Contributor
Sep 21, 2011
18,333
2
8,878
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
  • Like
Reactions: andres0185

Rgodoy8080

Member
Jan 6, 2021
36
3
Gentlemen moderators of this forum I have a moto e5 play pettyl with Android go
The problem with this device is that android go and does not have access to notifications and some and apps need these permissions to function correctly
? By far I ask you and any way to solve that problem?
I hope and you can help me thanks
 

H2-san

Member
Oct 4, 2021
5
0
I require assistance with my Motorola E5 Plus (Model hannah XT1924-7) - my bootloader correctly detects the IMEI, but no system - stock or LineageOS - can detect the IMEI of my phone. Someone help!

(Details spoilered below - TWRP erased all partitions before I dare to continue so we have a blank slate)
(bootloader) version: 0.5 (bootloader) version-bootloader: moto-msm8940-BF.C8 (bootloader) product: hannah (bootloader) board: hannah (bootloader) secure: yes (bootloader) hwrev: P3 (bootloader) radio: 6 (bootloader) storage-type: emmc (bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003 (bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F (bootloader) cpu: MSM8940 (bootloader) serialno: [Censored] (bootloader) cid: 0x0015 (bootloader) channelid: 0x8e (bootloader) uid: [Censored] (bootloader) securestate: flashing_unlocked (bootloader) iswarrantyvoid: yes (bootloader) max-download-size: 535822336 (bootloader) reason: Volume down key pressed (bootloader) imei: [Censored - correctly detected] (bootloader) meid: (bootloader) date: 07-19-2018 (bootloader) sku: XT1924-7 (bootloader) carrier_sku: XT1924-7 (bootloader) battid: (bootloader) iccid: (bootloader) cust_md5: (bootloader) max-sparse-size: 268435456 (bootloader) current-time: (bootloader) ro.build.fingerprint[0]: motorola/hannah_t/hannah:8.0.0/OCP (bootloader) ro.build.fingerprint[1]: S27.91-150-11-12/24:user/release-k (bootloader) ro.build.fingerprint[2]: eys (bootloader) poweroffalarm: 0 (bootloader) ro.build.version.full[0]: Blur_Version.27.401.24.hannah_t.t (bootloader) ro.build.version.full[1]: .en.US (bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0 (bootloader) version-baseband[0]: M8940TMO_34.26.11.76.01u HANNAH_NA_TMO (bootloader) version-baseband[1]: _CUST (bootloader) kernel.version[0]: Linux version 3.18.71-perf-g45127c1368cb (bootloader) kernel.version[1]: ([email protected]) (gcc version 4.8 ( (bootloader) kernel.version[2]: GCC) ) #1 SMP PREEMPT Tue Jun 2 21:22:57 (bootloader) kernel.version[3]: CDT 2020 (bootloader) sbl1.git: git=MBM-NG-VBF.C8-0-g8ffb6ee (bootloader) rpm.git: git=02a07261-dirty (bootloader) tz.git: git=deebf29353-dirty (bootloader) devcfg.git: git=deebf29353-dirty (bootloader) keymaster.git: git=deebf29353 (bootloader) cmnlib.git: git=deebf29353 (bootloader) cmnlib64.git: git=deebf29353 (bootloader) prov.git: git=deebf29353-dirty (bootloader) aboot.git: git=MBM-NG-VBF.C8-0-g4e376e8 (bootloader) frp-state: no protection (0) (bootloader) ro.carrier: metropcs (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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    [Help Thread]
    This thread has been created for
    Questions & Answers/Troubleshooting

    Specific to
    2018
    Moto E 5

    Moto E5 Plus

    Moto E5 Play/Cruise




    Please feel free to share issues, questions and offer help. Noob questions are welcomed.

    It is always best to use the Thanks button , in lieu of simply posting "Thank you".
    attachment.php

    Please keep discussion focused, on questions pertaining to this Device
    attachment.php
    List of supporters
    ... ... ... ...​

    To those seeking help:
    Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @. If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you! Supporters: If you want to be put on or off the list, just make a request here in the thread!​
    Before posting anything, I strongly advise you to read

    Please look for a similar thread when visiting another device forum.
    If you would like to create a [Help Thread] please Click Here.
    3
    I'm not planning on adding every Rom or Mod,
    but if you have a suggestion for other links
    Please post them here.

    Please try post
    Model #, software channel, and codename with your question
    eg: XT1921-1, Retail, RJames
    See my Moto Flashing Guide






    FAQs

    Custom Roms/Recovery/Root/



    Firmware




    Specs



    Moto E5 4G/LTE
    •XT1944-1 Moto E5 Sng SIM Retail (Nora)
    •XT1944-2 Moto E5 Dual SIM Retail (Nora)
    •XT1944-3 Moto E5 Sng SIM Retail (Nora)
    •XT1944-4 Moto E5 Dual SIM Retail (Nora)
    •XT1944-5 Moto E5 Dual SIM Retail (Nora)
    •XT1944-6 Moto E5 Dual SIM Retail (Nora)


    Moto E5 Play/Cruise
    •XT1920 Moto E5 Play Android Go (PettyL)
    •XT1921-1 Moto E5 Play Sng SIM Retail (RJames)
    •XT1921-2 Moto E5 Cruise Cricket (James)
    •XT1921-3 Moto E5 Play T-Mobile (James)
    •XT1921-5 Moto E5 Play Sprint (James)
    •XT1921-6 Moto E5 Play Verizon (RJames)


    Moto E5 Plus






    https://www.xda-developers.com/motorola-moto-g6-moto-e5-series-poor-software-support/


    Root
    https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182
    2
    Thanks for your help!
    OK, so I followed all the instructions, (using the XT1944-4 firmware & Magisk 17.1) and everything appeared to go well except for one error message when running fastboot flash boot patched-boot.img :


    Now when I try to reboot the device I see N/A on the screen for a few seconds, and then the intro 'moto' animation runs, and just keeps looping over and over.
    Do you have any suggestions for what I can try next?
    Ok. The error message you received flashing the patched boot.img, as well as the "N/A" or "Bad Key" notifications during boot, are all completely normal. (There are custom boot logos made especially to hide the boot notifications). As for your perpetual boot loop, I'll try and help you fix this. First, on your xt1944-6, who is your mobile provider? Also, please specify the build of firmware you are running Lastly, do you have TWRP installed on your device?
    2
    Very helpful information as far as how your Boost is restricted. If I get what you're saying than the Android image just prevents you from using GSM settings, or is it not registering the sim card? I ran into some of that nonsense with Oreo 8.1 with my Pixel when trying to change APN settings with a Verizon MNVO sim card (it doesn't let you, hooray for Google-supported lockdowns).

    I suppose with these branded phones showing such restrictions the only safe bet for phones that Verizon would allow me to activate to their network (or an MVNO of theirs) would be the Verizon Moto E5 play or the stock-unlocked one then? Is it safe to assume one cannot do the opposite of what you tried, and try to use an eBay unlock code (assuming that's even applicable for the cricket one) on a Boost, Virgin Mobile or Cricket-branded phone, and hope that the activation for Verizon would work? I imagine Verizon would not let the IMEI pass the smell test as they'd know it was a model from a competitor? Perhaps with the Cricket/Boost version they might even try to lock-down the CDMA (or Verizon LTE Band 13) radios (even though by pure spec-sheet this phone COULD work on any of the Big 4 and I thinking that's how the xt1921-1 works).
    Yeah the 1921-1 should operate on any one of the Big 4 (or rather the Big 3 now that Sprint & T-Mobile have entered into a preemptory merger).
    Sprint traditionally locked its Moto devices (e.g. Moto E LTE, Moto G3) by embedding encryption to read-only partitions such as /pds, /hob, /dhob. With the Moto E4 and Moto E5 Play, Sprint (and its subsidiaries) are taking the less restricted firmware route to restrict GSM support, which is surmountable by the installation of custom ROMs and some root modding. As far as LTE bands go, Qualcomm's QFIL and QPST can be used to enable bands otherwise restricted by a provider. There are some excellent guides here on XDA on how-to and resources.
    I agree that you should have no problems whatsoever getting a Verizon branded Moto E5 Play and using it on a Verizon subsidiary or mvno. While I cannot confirm, I have heard members report that unlock codes from eBay are effective in carrier unlocking the Verizon Moto E5 Play. (However, please keep in mind that the Verizon variant cannot be bootloader unlocked. Thus, root cannot be achieved). However, this is nothing new for Verizon branded devices. They lock the majority of their devices down. One of my most frequent sayings is -- if you want root, don't buy a Verizon branded device.
    2
    I am very close to buying a Moto E5 Play for my aunt. The last question I hope to clarify here before I pick where to buy it from is as follows:

    Are the Moto E5 Play phones sold (Branded) by companies like Verizon, Boost Mobile, and Virgin Mobile SIM locked? Does anyone know how hard it would be to buy a Verizon-branded E5 Play and activate it on a Verizon MNVO carrier (like Red Pocket-V or US Mobile)?

    I noticed in an earlier post someone confirmed the T-Mobile variant can be bootloader unlocked but I'm not sure there were details about a SIM/Carrier lock.

    I'm noticing a lack of an E5 phone for sale anywhere as just plain "unlocked" or buying direct from Motorola for this phone in US Retail markets.
    I'm familiar with four different variants of the Moto E5 Play. The xt1921-2 is the Cricket model, branded under the name Moto E5 Cruise; the xt1921-5 is the Sprint, Virgin Mobile, Boost Mobile model; the xt1921-6 is the Verizon model; and there is a xt1921-1 variant which is the factory unlocked, single SIM retail model. The retail model is of course factory unlocked to operate on any GSM provider. However, this is the only model that I can confirm is not network restricted in any way.