Moto E5 play XT1921-3 (James T-Mobile variant) won't read sim card after flashing stock firmware

Search This thread
Jan 9, 2021
7
0
It all started when I wanted to root my phone so that I could move more apps to my sd card. I followed this tutorial: https://www.theworldsbestandworst.com/2020/06/root-motorola-moto-e5-play/ but the version of SuperSU they had me install bricked my phone (My phone would freeze on startup at the t-mobile logo).

So, having done so in the past, I knew I could flash the stock firmware and hopefully get my phone back to working condition. I tried using two different downloads of the stock firmware. One from here: https://sourceforge.net/projects/moto-e5-firmware/files/JAMES/XT1921-3/ and one from here: https://forum.xda-developers.com/t/...he-e5-play-xt1921-3-t-mobile-variant.3839675/ (it's the link first given by timjames474). For both downloads I used the batch file method of flashing described here:
because RSDLite wasn't detecting my device. However, both of the times I tried flashing the stock firmware my phone worked normally but was unable to detect my sim card.

Was I using the wrong download of stock firmware? Is my phone broken for good? Please help me.
 

sd_shadow

Recognized Contributor
It all started when I wanted to root my phone so that I could move more apps to my sd card. I followed this tutorial: https://www.theworldsbestandworst.com/2020/06/root-motorola-moto-e5-play/ but the version of SuperSU they had me install bricked my phone (My phone would freeze on startup at the t-mobile logo).

So, having done so in the past, I knew I could flash the stock firmware and hopefully get my phone back to working condition. I tried using two different downloads of the stock firmware. One from here: https://sourceforge.net/projects/moto-e5-firmware/files/JAMES/XT1921-3/ and one from here: https://forum.xda-developers.com/t/...he-e5-play-xt1921-3-t-mobile-variant.3839675/ (it's the link first given by timjames474). For both downloads I used the batch file method of flashing described here:
because RSDLite wasn't detecting my device. However, both of the times I tried flashing the stock firmware my phone worked normally but was unable to detect my sim card.

Was I using the wrong download of stock firmware? Is my phone broken for good? Please help me.
What does getvar all say?
Code:
fastboot getvar all
 
Jan 9, 2021
7
0
What does getvar all say?
Code:
fastboot getvar all

Here is what my terminal returns when I enter getvar all:

(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.45
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(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: MSM8920
(bootloader) serialno: ZY323SRCZP
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 09E5223100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146092420788
(bootloader) meid:
(bootloader) date: 03-18-2019
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-51-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.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-g5480efb-0001
(bootloader) kernel.version[1]: 6-gd2768b6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 20 10:36:48 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB9.45-0-geb7a3e0
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=5fefee4-dirty
(bootloader) devcfg.git: git=5fefee4-dirty
(bootloader) keymaster.git: git=5fefee4
(bootloader) cmnlib.git: git=5fefee4
(bootloader) cmnlib64.git: git=5fefee4
(bootloader) prov.git: git=5fefee4-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.45-0-gff56367
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(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.772s
 

sd_shadow

Recognized Contributor
Here is what my terminal returns when I enter getvar all:

(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.45
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(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: MSM8920
(bootloader) serialno: ZY323SRCZP
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 09E5223100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146092420788
(bootloader) meid:
(bootloader) date: 03-18-2019
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-51-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.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-g5480efb-0001
(bootloader) kernel.version[1]: 6-gd2768b6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 20 10:36:48 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB9.45-0-geb7a3e0
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=5fefee4-dirty
(bootloader) devcfg.git: git=5fefee4-dirty
(bootloader) keymaster.git: git=5fefee4
(bootloader) cmnlib.git: git=5fefee4
(bootloader) cmnlib64.git: git=5fefee4
(bootloader) prov.git: git=5fefee4-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.45-0-gff56367
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(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.772s
The firmware you are using should be correct.
getvar say baseband is missing
Code:
(bootloader) version-baseband: <not found>
and both system slots are INVALID
Not a good sign.
You didn't see any flashing errors?

RSD Lite doesn't work with Windows 10, do you have a Windows 7 machine?

Try posting the service.xml text in https://kfhost.net/flashfile
and compare with your batch file.
 
Jan 9, 2021
7
0
The firmware you are using should be correct.
getvar say baseband is missing
Code:
(bootloader) version-baseband: <not found>
and both system slots are INVALID
Not a good sign.
You didn't see any flashing errors?

RSD Lite doesn't work with Windows 10, do you have a Windows 7 machine?

Try posting the service.xml text in https://kfhost.net/flashfile
and compare with your batch file.

The batch file I had was slightly different than the one produced by the website you had me use. I replaced the batch file's contents and flashed the firmware again. I got these errors (not sure if 'image signed with key bad key' is an error so I'm including it just incase):

(bootloader) is-logical:FSG: not found
Sending 'FSG' (1696 KB) OKAY [ 0.222s]
Writing 'FSG' (bootloader) Invalid partition name FSG
FAILED (remote: '')
fastboot: error: Command failed

(bootloader) is-logical:DSP: not found
Sending 'DSP' (16384 KB) OKAY [ 0.689s]
Writing 'DSP' (bootloader) Invalid partition name DSP
FAILED (remote: '')
fastboot: error: Command failed

(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.526s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.553s]
Finished. Total time: 1.279s

(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.698s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.584s]
Finished. Total time: 1.316s

I got the same bad key errors when I flashed the firmware with my first batch file. After this flash the phone still works normally besides not being able to read the sim card.
 

sd_shadow

Recognized Contributor
The batch file I had was slightly different than the one produced by the website you had me use. I replaced the batch file's contents and flashed the firmware again. I got these errors (not sure if 'image signed with key bad key' is an error so I'm including it just incase):

(bootloader) is-logical:FSG: not found
Sending 'FSG' (1696 KB) OKAY [ 0.222s]
Writing 'FSG' (bootloader) Invalid partition name FSG
FAILED (remote: '')
fastboot: error: Command failed

(bootloader) is-logical:DSP: not found
Sending 'DSP' (16384 KB) OKAY [ 0.689s]
Writing 'DSP' (bootloader) Invalid partition name DSP
FAILED (remote: '')
fastboot: error: Command failed

(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.526s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.553s]
Finished. Total time: 1.279s

(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.698s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.584s]
Finished. Total time: 1.316s

I got the same bad key errors when I flashed the firmware with my first batch file. After this flash the phone still works normally besides not being able to read the sim card.
Strange you shouldn't have a recovery.img
Can you attach the service.xml ?
 

sd_shadow

Recognized Contributor
I did have twrp on my phone before the flash
Devices with a/b system slots don't have a recovery partition it's part of the boot.img now
so now when you install Twrp or magisk the boot partition must be changed.
Here's the servicefile.xml, the firmware doesn't have a service.xml:
Yes, my bad
 
Jan 9, 2021
7
0
If it's XP or 7 you could try RSD Lite
With the current machine, have you updated adb files?
Tried different USB ports?

The other pc is also windows 10 :( .

I'm using the most current platform-tools.

I'll try using other usb ports but my computer doesn't have trouble connecting to my phone so I'm not sure how that'd help (or if your talking about trying to get RSD Lite to work I've already tried other usb ports).
 

muneebwolf

Member
Feb 9, 2021
9
0
Man any solutions? I reinstalled firmware, after unlocking bootloader then I flashed twrp and magisk using that twrp but my baseband version is unknown, IMEI unknown.
but my Wi-Fi is working fine, Can someone guide me through with it?
 

muneebwolf

Member
Feb 9, 2021
9
0
What does getvar all say?
Code:
 fastboot getvar all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(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: MSM8920
(bootloader) serialno: ZY323JV88W
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: B94B05DB00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146091881899
(bootloader) meid:
(bootloader) date: 12-17-2018
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 9:35:18 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-150-5-1-3/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.311.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.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-gf60ba68 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue May 7 15:58:26 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=7a51f9f-dirty
(bootloader) devcfg.git: git=7a51f9f-dirty
(bootloader) keymaster.git: git=7a51f9f
(bootloader) cmnlib.git: git=7a51f9f
(bootloader) cmnlib64.git: git=7a51f9f
(bootloader) prov.git: git=7a51f9f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(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
 

sd_shadow

Recognized Contributor
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(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: MSM8920
(bootloader) serialno: ZY323JV88W
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: B94B05DB00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146091881899
(bootloader) meid:
(bootloader) date: 12-17-2018
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 9:35:18 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-150-5-1-3/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.311.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.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-gf60ba68 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue May 7 15:58:26 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=7a51f9f-dirty
(bootloader) devcfg.git: git=7a51f9f-dirty
(bootloader) keymaster.git: git=7a51f9f
(bootloader) cmnlib.git: git=7a51f9f
(bootloader) cmnlib64.git: git=7a51f9f
(bootloader) prov.git: git=7a51f9f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(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
Looks like you have this version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-5-1-3_cid21_subsidy-MPCS_RSU_regulatory-DEFAULT_CFC.xml.zip
this is the newest version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-14-13_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip


but that shouldn't have anything do with your problem, unless you have been flashing a different version than 27.91-150-5-1-3

The invalid slots are worrisome, often with this problem, a blankflash is needed to fix it.

Are you using flashfile.xml to get the correct flash commands?
 

muneebwolf

Member
Feb 9, 2021
9
0
Looks like you have this version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-5-1-3_cid21_subsidy-MPCS_RSU_regulatory-DEFAULT_CFC.xml.zip
this is the newest version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-14-13_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip


but that shouldn't have anything do with your problem, unless you have been flashing a different version than 27.91-150-5-1-3

The invalid slots are worrisome, often with this problem, a blankflash is needed to fix it.

Are you using flashfile.xml to get the correct flash commands?

Man I used downloaded this firmware from lolinet, used all the necessary commands but still its not working, and yes I used flashfile.xml
 

Top Liked Posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone