Moto G6 Play not recognizing sim card

Avakin

Member
Jun 14, 2019
6
0
0
Need help, tried to downgrade a Moto G6 Play, unlocked bootloader then flashed, after this the phone service stopped working, and it isn't recognizing the Sim card.

Reflashed the stock rom to no avail.

Trying to see imei and getting no answer, and in the fastboot baseband is described has not found. Wifi is working fine.

getvar all returned:

(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(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: MSM8937
(bootloader) serialno: 0047501565
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 35EA128F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355568092781837
(bootloader) meid:
(bootloader) date: 06-08-2018
(bootloader) sku: XT1922-5
(bootloader) carrier_sku: XT1922-5
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 29 18:37:43 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:9/PPP29.5
(bootloader) ro.build.fingerprint[1]: 5-25/08c6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.26.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g90c1846 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Tue Jan 29 12:40:44 CST 2019
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-b867b3e-190122
(bootloader) rpm.git: MBM-2.1-aljeter_retail-099a494-dirty-190129
(bootloader) tz.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) prov.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) aboot.git: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(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

Thank you all in advance.
 

Starkiller2

Senior Member
May 2, 2018
306
150
0
phoenix
Mount persist in TWRP. From adb shell type

chmod 0700 /persist/rfs/msm/mpss/datablock/id_00

Reboot. Give it a few minutes to provision

---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------

Need help, tried to downgrade a Moto G6 Play, unlocked bootloader then flashed, after this the phone service stopped working, and it isn't recognizing the Sim card.

Reflashed the stock rom to no avail.

Trying to see imei and getting no answer, and in the fastboot baseband is described has not found. Wifi is working fine.

getvar all returned:

(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(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: MSM8937
(bootloader) serialno: 0047501565
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 35EA128F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355568092781837
(bootloader) meid:
(bootloader) date: 06-08-2018
(bootloader) sku: XT1922-5
(bootloader) carrier_sku: XT1922-5
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 29 18:37:43 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:9/PPP29.5
(bootloader) ro.build.fingerprint[1]: 5-25/08c6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.26.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g90c1846 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Tue Jan 29 12:40:44 CST 2019
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-b867b3e-190122
(bootloader) rpm.git: MBM-2.1-aljeter_retail-099a494-dirty-190129
(bootloader) tz.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) prov.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) aboot.git: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(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

Thank you all in advance.
Also, you need to reflash your bootloader
 

Avakin

Member
Jun 14, 2019
6
0
0
Mount persist in TWRP. From adb shell type

chmod 0700 /persist/rfs/msm/mpss/datablock/id_00

Reboot. Give it a few minutes to provision

---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------


Also, you need to reflash your bootloader
Can you guide through the persist process?

Also, every time I flash the bootloadeer it gives me a bad image error.
 

Starkiller2

Senior Member
May 2, 2018
306
150
0
phoenix
Then you're flashing the wrong bootloader
In twrp hit the mount button, you should see persist listed.
Check the box, that should mount it.

And are you flashing the boot image or the bootloader? What's your model, and what firmware are you flashing?

Wait, it's not reading the iccid through fastboot. Check the Sim tray. Even without service it should still see it in fastboot
 
  • Like
Reactions: Spaceminer

Avakin

Member
Jun 14, 2019
6
0
0
Then you're flashing the wrong bootloader
In twrp hit the mount button, you should see persist listed.
Check the box, that should mount it.

And are you flashing the boot image or the bootloader? What's your model, and what firmware are you flashing?

Wait, it's not reading the iccid through fastboot. Check the Sim tray. Even without service it should still see it in fastboot
Getvar all with the sim inserted:

(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(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: MSM8937
(bootloader) serialno: 0047501565
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 35EA128F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355568092781837
(bootloader) meid:
(bootloader) date: 06-08-2018
(bootloader) sku: XT1922-5
(bootloader) carrier_sku: XT1922-5
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 28 19: 0:39 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:9/PPP29.5
(bootloader) ro.build.fingerprint[1]: 5-25/08c6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.26.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g90c1846 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Tue Jan 29 12:40:44 CST 2019
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-b867b3e-190122
(bootloader) rpm.git: MBM-2.1-aljeter_retail-099a494-dirty-190129
(bootloader) tz.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) prov.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) aboot.git: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(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

The persist folder doesn't exist, how should I proceed?
 

Spaceminer

Senior Member
Sep 9, 2016
1,159
548
123
Olympus Mons
Getvar all with the sim inserted:

The persist folder doesn't exist, how should I proceed?
Flash the same firmware your were last on for the aljeter, or one that's later. Your bootloader says this is your firmware. It also says your carrier is Brazil. So, if that first one doesn't work then try this one. If the firmware you flashed was too old the sim card won't be read properly. I've been through this before.
 

Avakin

Member
Jun 14, 2019
6
0
0
Flash the same firmware your were last on for the aljeter, or one that's later. Your bootloader says this is your firmware. It also says your carrier is Brazil. So, if that first one doesn't work then try this one. If the firmware you flashed was too old the sim card won't be read properly. I've been through this before.
I've got some errors during the flash:

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 failure)

writing 'boot'...
(bootloader) Image signed with key bad key

And I have the bad key error while turning it on, when I try to lock the bootloader, it tells me to allow unlock on dev settings, there it doesn't let me, telling its already unlocked. This happened with the first link, should I try with the other one?
 

Spaceminer

Senior Member
Sep 9, 2016
1,159
548
123
Olympus Mons
I've got some errors during the flash:

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 failure)

writing 'boot'...
(bootloader) Image signed with key bad key

And I have the bad key error while turning it on, when I try to lock the bootloader, it tells me to allow unlock on dev settings, there it doesn't let me, telling its already unlocked. This happened with the first link, should I try with the other one?
Bad key is normal, it'll say that even if the firmware is correct. That just happens because the bootloader is unlocked. The flash errors you encountered are also normal. It just means the bootloader and gpt.bin you're flashing are older than your current one. That's not a problem. You can just skips those. If everything on your phone is working correctly, then you don't need to try any other firmware.

You don't need to relock your bootloader to do anything, or take an OTA update. Why are you trying to?

Edit: You can hide the bad key message by flashing any of my boot logos in twrp. All of them will hide it except the original one. There's also a couple a few posts down. If you plan on taking an OTA, don't do this until after taking the update. Otherwise the ota will fail since you've modified the stock firmware.
 
Last edited:

Avakin

Member
Jun 14, 2019
6
0
0
Bad key is normal, it'll say that even if the firmware is correct. That just happens because the bootloader is unlocked. The flash errors you encountered are also normal. It just means the bootloader and gpt.bin you're flashing are older than your current one. That's not a problem. You can just skips those. If everything on your phone is working correctly, then you don't need to try any other firmware.

You don't need to relock your bootloader to do anything, or take an OTA update. Why are you trying to?

Edit: You can hide the bad key message by flashing any of my boot logos in twrp. All of them will hide it except the original one. There's also a couple a few posts down. If you plan on taking an OTA, don't do this until after taking the update. Otherwise the ota will fail since you've modified the stock firmware.
Neither firmwares worked, even the signal symbol doesn't appear when the phone is on. What more can I do?
 

Spaceminer

Senior Member
Sep 9, 2016
1,159
548
123
Olympus Mons
Neither firmwares worked, even the signal symbol doesn't appear when the phone is on. What more can I do?
1. Did you follow all the commands in the flash file of the firmware, such as wipe modemst1, cache, userdata?

2. Can you navigate to settings > Network & Internet > mobile network > Preferred Network Type? If so are there any options.

3. Can you also send me screen shot? I just need to see the status bar. It helps if I can see what you see.
 

ninjakira

Senior Member
Nov 6, 2016
539
244
33
29
batavia, ohio
Where are you from my guy? are you from USA or Brazil? And where did you buy your phone.

---------- Post added at 11:04 PM ---------- Previous post was at 10:58 PM ----------

Your sku says xt1922-5 that means you more than likely have retbr. Here is your stock firmware. https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETBR/ just follow my guide and reflash and you should be good. If you don't remember what firmware you were on before just flash the most recent Oreo firmware if you want to be on Oreo. if it says anything like security downgrade then start from the first 9.0 firmware until one works with Mobile data working.

---------- Post added at 11:15 PM ---------- Previous post was at 11:04 PM ----------

Also to just avoid the security downgrade stuff please DO NOT use these following adb commands while flashing the firmwares. it will be easier for us sort of

fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin

Remember DO NOT not use these while flashing lol
 
Last edited: