Develop Bugs

Moto G6 Play not recognizing sim card

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.

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 ----------
Avakin said:
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.
Click to expand...
Click to collapse
Also, you need to reflash your bootloader

Double

Starkiller2 said:
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
Click to expand...
Click to collapse
Can you guide through the persist process?
Also, every time I flash the bootloadeer it gives me a bad image error.

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

Starkiller2 said:
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
Click to expand...
Click to collapse
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?

Avakin said:
Getvar all with the sim inserted:
The persist folder doesn't exist, how should I proceed?
Click to expand...
Click to collapse
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.

Spaceminer said:
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.
Click to expand...
Click to collapse
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?

Avakin said:
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?
Click to expand...
Click to collapse
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.

Spaceminer said:
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.
Click to expand...
Click to collapse
Neither firmwares worked, even the signal symbol doesn't appear when the phone is on. What more can I do?

Avakin said:
Neither firmwares worked, even the signal symbol doesn't appear when the phone is on. What more can I do?
Click to expand...
Click to collapse
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.

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

Is it possible to root the T-Mobile XT1789-04?????

I've been trying to root and install Lineage 16.0 on my Z2 force TMO XT1789-04 for a few weeks now.
I was able to unlock the bootloader on Motorola's website no problem.
The phone has been updated to OCXS 27.1.7.
When I run getprop ro.bootloader, MBM-3.0-nash_tmo-1f35305-190705 is my result. This didn't verify if my bootloader was OCSX, so I ran the getvar all command in fastboot, and the output said I was running MBM-3.0-nash_tmo-1f35305-190705 in slot _b. I will post all the info at the end of the post.
Earlier I made the mistake of moving ahead to set the bootloader partition to slot _a. Luckilly I didn't brick my phone. I used the following commands with no luck .
fastboot set_active other
fastboot set_active a
fastboot –set-active=_aslot
fastboot –set-active=_a
What am I doing wrong? Should I give up? I'd rather sell my phone than brick it.
If someone could point me in the right direction I'd appreciate it!!!.
Thanks!
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224B9BP4
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 14905111
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ****(deleted)
(bootloader) meid:
(bootloader) date: 07-26-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4379
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) gitrov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6

Why do u have to do all of this to just install lineage 16?
I'm on T-Mobile too and I just simply:
1- fastboot flashed the pre-los zip
2- follow the normal procedure for flashing Los (although it took time to find the right twrp version actually working, many didn't flashed successfully) + magisk for root
3- mind my tmo Z2 force was already on Oreo...

Use twrp 3.3.0.0.img to flash with, I wouldn't worry about installing twrp since the updater uses Los recovery. If you must insstall twrp 3.3.1.0.zip is solid I believe. Not sure why 3..3.0.0.zip isn't there, but I have the zip if needed.

I tried to install TWRP 3.3.0-0 using fastboot flash boot (path to) twrp.img
I wasn't able to get TWRP installed. Am I using the wrong commands or twrp image?

Google_is_Watching said:
I tried to install TWRP 3.3.0-0 using fastboot flash boot (path to) twrp.img
I wasn't able to get TWRP installed. Am I using the wrong commands or twrp image?
Click to expand...
Click to collapse
You'll need to run fastboot boot twrp.img once it boots to TWRP you can use the install option within TWRP to install the twrp.zip file

rcmaehl said:
You'll need to run fastboot boot twrp.img once it boots to TWRP you can use the install option within TWRP to install the twrp.zip file
Click to expand...
Click to collapse
It worked!!! I feel dumb but grateful. Thank you!

XT1952-1 boot.img issues

Hi!
I'm new here, and some threads have been helpful already. However, I wonder if trying other different approaches might make the issue more complicated than it needs to be. Also, this isn't urgent, and I'd rather do it right than fudge around more than I already have..
I'm currently stuck with a "bad key" in the top left corner when booting the phone. I can still boot into bootloader and fastboot detects the device. I've tried overwriting the boot.img with a variety of variants, hoping it would work out, but alas it has not. I can boot into TWRP (phone wouldn't accept TWRP install from the start, but that's okay) but when I attempt to flash a LOS zip via sideload, it returns some errors.
I had originally installed a LOS + MicroG variant, which was working great, and then wanted to lock the bootloader. Well, and here I am..
From what I can tell, I shouldn't have to blankflash just yet. However, I'm not quite sure what the easiest path out of this pickle is. Thoughts?
Edit: I should add LMSA returns an issue when attempting to download software for the device. I tried setting it to a different XT variant, and it correctly recognizes the device, but then returns an "improper settings" message, if I remember right.
This is what getvar returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-channel_retail-a5c9d71-190702
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVTB
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: D6D709D800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 03-28-2019
(bootloader) sku: XT1952-1
(bootloader) carrier_sku: XT1952-1
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 13 21:45: 9 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/channel_reteu/channel:9/P
(bootloader) ro.build.fingerprint[1]: PY29.105-134/e13ed:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.156.channel_r
(bootloader) ro.build.version.full[1]: eteu.retail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband[0]: M632_26.100.01.120.01R CHANNEL_SUPERDS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf ([email protected]
(bootloader) kernel.version[1]: lbld71) (gcc version 4.9.x 20150123 (pre
(bootloader) kernel.version[2]: release) (GCC) ) #1 SMP PREEMPT Tue Jul
(bootloader) kernel.version[3]: 2 04:04:07 CDT 2019
(bootloader) sbl1.git: MBM-2.1-channel_retail-b508f3a-190702
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab3-190702
(bootloader) tz.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) devcfg.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) keymaster.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) cmnlib.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) cmnlib64.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) prov.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) aboot.git: MBM-2.1-channel_retail-a5c9d71-190702
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: timit
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 6
Thanks for any help in advance!

danheg said:
Hi!
I'm new here, and some threads have been helpful already. However, I wonder if trying other different approaches might make the issue more complicated than it needs to be. Also, this isn't urgent, and I'd rather do it right than fudge around more than I already have..
I'm currently stuck with a "bad key" in the top left corner when booting the phone. I can still boot into bootloader and fastboot detects the device. I've tried overwriting the boot.img with a variety of variants, hoping it would work out, but alas it has not. I can boot into TWRP (phone wouldn't accept TWRP install from the start, but that's okay) but when I attempt to flash a LOS zip via sideload, it returns some errors.
I had originally installed a LOS + MicroG variant, which was working great, and then wanted to lock the bootloader. Well, and here I am..
From what I can tell, I shouldn't have to blankflash just yet. However, I'm not quite sure what the easiest path out of this pickle is. Thoughts?
Edit: I should add LMSA returns an issue when attempting to download software for the device. I tried setting it to a different XT variant, and it correctly recognizes the device, but then returns an "improper settings" message, if I remember right.
This is what getvar returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-channel_retail-a5c9d71-190702
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVTB
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: D6D709D800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 03-28-2019
(bootloader) sku: XT1952-1
(bootloader) carrier_sku: XT1952-1
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 13 21:45: 9 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/channel_reteu/channel:9/P
(bootloader) ro.build.fingerprint[1]: PY29.105-134/e13ed:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.156.channel_r
(bootloader) ro.build.version.full[1]: eteu.retail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband[0]: M632_26.100.01.120.01R CHANNEL_SUPERDS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf ([email protected]
(bootloader) kernel.version[1]: lbld71) (gcc version 4.9.x 20150123 (pre
(bootloader) kernel.version[2]: release) (GCC) ) #1 SMP PREEMPT Tue Jul
(bootloader) kernel.version[3]: 2 04:04:07 CDT 2019
(bootloader) sbl1.git: MBM-2.1-channel_retail-b508f3a-190702
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab3-190702
(bootloader) tz.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) devcfg.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) keymaster.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) cmnlib.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) cmnlib64.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) prov.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) aboot.git: MBM-2.1-channel_retail-a5c9d71-190702
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: timit
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 6
Thanks for any help in advance!
Click to expand...
Click to collapse
This should be your firmware
https://mirrors.lolinet.com/firmware/moto/channel/official/TIMIT/
XT1952-1_CHANNEL_TIMIT_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
There are newer versions like this Android 10
XT1952-1_CHANNEL_TIMIT_10_QPYS30.52-22-8-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I would start with the version you have.
Download the firmware, unzip, find the flash.file.xml, open it with a text editor, copy, and paste into the online flash.file convertor, link in my thread.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

Thanks! I'm trying it now.
I do get "(bootlaoder) is-logical:system_a: not found" (or a corresponding similarity) for almost every line. Also, boot.img still returns a "bad key" during flash.
Device reboots, and I get a "bad key," but it reboots into the operating system.
That should allow me to reinstall LOS, or at least I can try and see if it'll do so.

danheg said:
Thanks! I'm trying it now.
I do get "(bootlaoder) is-logical:system_a: not found" (or a corresponding similarity) for almost every line. Also, boot.img still returns a "bad key" during flash.
Device reboots, and I get a "bad key," but it reboots into the operating system.
That should allow me to reinstall LOS, or at least I can try and see if it'll do so.
Click to expand...
Click to collapse
Bad key is pretty common for moto devices with unlocked bootloader, usually just means the boot.img isn't signed the way it expected.

Okay. 18.1 + MicroG running again. I'm also getting the N/A on boot again, as I did last time.
Big thanks for that! I had been plucking the boot.img out of of zips in the expectation that it would eventually work. Didn't realize I needed to flash the whole system.
I found myself in this mess because I wasn't able to properly lock the bootloader. Unless there are specific suggestions on what I should try or do better, I'd just leave it open. It bugs me a little, but it's not a huge issue.

danheg said:
Okay. 18.1 + MicroG running again. I'm also getting the N/A on boot again, as I did last time.
Big thanks for that! I had been plucking the boot.img out of of zips in the expectation that it would eventually work. Didn't realize I needed to flash the whole system.
I found myself in this mess because I wasn't able to properly lock the bootloader. Unless there are specific suggestions on what I should try or do better, I'd just leave it open. It bugs me a little, but it's not a huge issue.
Click to expand...
Click to collapse
Moto's must be completely stock to Relock the bootloader, and even then it can be tricky.

Okay. What I take away from that is that it's difficult, if not impossible, to re-lock the bootloader of a Motorola loaded with Lineage?

danheg said:
Okay. What I take away from that is that it's difficult, if not impossible, to re-lock the bootloader of a Motorola loaded with Lineage?
Click to expand...
Click to collapse
Do not lock a moto device with a custom rom, unless you don't want it to work ever again.

Question Moto e 2020 XT2052-1 Startup Fail

Hello, I have this device with problems booting android 10. A red legend appears showing "
Failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fail-through from factory boot mode "
I have tried to flash it with various tools like RSD Lite, Odin(NOT shown), and Lenovo User Assistant, all efforts have failed the device always shows the same red legend or sometimes it goes completely black with the charging indicator led blinking. Recovery mode is not accessible.
Please help. Thanks in advance

Rainwod said:
Hello, I have this device with problems booting android 10. A red legend appears showing "
Failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fail-through from factory boot mode "
I have tried to flash it with various tools like RSD Lite, Odin(NOT shown), and Lenovo User Assistant, all efforts have failed the device always shows the same red legend or sometimes it goes completely black with the charging indicator led blinking. Recovery mode is not accessible.
Please help. Thanks in advance
Click to expand...
Click to collapse
What does getvar all say? Remove imei before posting
Code:
fastboot getvar all

thanks sd_shadow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY22BLLKRM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 96F6A8B300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from factory boot mode
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-18-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66368
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 9 8:41:56 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-135-7/c2ede:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.02R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Wed J
(bootloader) kernel.version[3]: un 9 05:43:55 CDT 2021
(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: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 1.609s
i downloaded and try to flash this ROMs:
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
GINNA_RETAIL_QPGS30.82_135_16_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
the variable (bootloader) ro.build.fingerprint[1] does not change its value, it always shows S30.82-135-7/c2ede:user/release-ke even after flashing with RSD Lite.
Thanks a lot

Rainwod said:
thanks sd_shadow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY22BLLKRM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 96F6A8B300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from factory boot mode
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-18-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66368
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 9 8:41:56 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-135-7/c2ede:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.02R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Wed J
(bootloader) kernel.version[3]: un 9 05:43:55 CDT 2021
(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: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 1.609s
i downloaded and try to flash this ROMs:
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
GINNA_RETAIL_QPGS30.82_135_16_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
the variable (bootloader) ro.build.fingerprint[1] does not change its value, it always shows S30.82-135-7/c2ede:user/release-ke even after flashing with RSD Lite.
Thanks a lot
Click to expand...
Click to collapse
Rsd lite may not work with Windows 10.
Use Windows 7 or xp with rsd lite.

Sometimes this works flash this.
Code:
fastboot flash partition gpt.bin
fastboot reboot bootloader
Then retry LMSA if you have Windows 10 or RSD Lite if you have Windows 7 or XP

sd_shadow said:
(...)
Then retry LMSA if you have Windows 10 or RSD Lite if you have Windows 7 or XP
Click to expand...
Click to collapse
I have tried both methods that you have indicated, in both cases ( RSD lite with Windows XP ) the process ends normally without failures but the result is the same, red Startup Fail legend. Thanks for the help, do you have any other ideas?

Rainwod said:
I have tried both methods that you have indicated, in both cases ( RSD lite with Windows XP ) the process ends normally without failures but the result is the same, red Startup Fail legend. Thanks for the help, do you have any other ideas?
Click to expand...
Click to collapse
It's possible the issue is related to the Persist Partition or other secure partition.
There is a good thread in the Moto G5 Plus forum.
I don't know if any of that discussion applies to the Moto E though.
Fix Persist, resolve IMEI=0, Volte, 4G, Explanation, Requirements
I have created this thread in order to have one thread that details just the solution to fixing your persist, identifying whether or not you have an issue with your persist, and how you can restore your IMEI without hacks. This guide is written...
forum.xda-developers.com

Honestly looks like a cross flash to retus, followed by a bootloader lock. I don't think you can trust any fastboot variables if that's the case. You'd just have to flash boot.img for every model and variant of the E 2020 until you find the one that is allowed to boot.

IMEI 0

HELLO EVERYONE! PLEASE HELP TO RESTORE IMEI MOTO Z2 FORCE (XT1789-04 TMOBILE)
SHORT STORY: I TRIED TO FLASH TO ANDROID 9 FROM VERIZON CARRIER, I UNLOCKED BOOTLOADER, BACKUP ALL DATA BY TWRP BUT I DID SOMETHING WRONG AND DELETED BACKED UP DATA BY MISTAKE.
USING MOTOROLA RESCUE I CAN RESTORE ORIGINAL FIRMWARE, BUT IMEI SHOWS 0, WIFI ALSO DOESN'T WORK.
COULD SOMEONE EXPLAIN HOW TO RESTORE EFS FOLDER , IS IT ANY SOLUTION AND EXPLANATION HOW TO DO IT.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224CBHHC
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 3C0920D9
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565**********
(bootloader) meid:
(bootloader) date: 07-30-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3785
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08u NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) gitrov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.229s

IMEI is not in Android/ROM, ist in PDS partition!
You hab a backup from all version with twrp?

R!ffRaff said:
IMEI is not in Android/ROM, ist in PDS partition!
You hab a backup from all version with twrp?
Click to expand...
Click to collapse
I did, but I formatted hard drive by mistake and lost it, now trying to restore imei and have no idei how to do it

khurshed04 said:
I did, but I formatted hard drive by mistake and lost it, now trying to restore imei and have no idei how to do it
Click to expand...
Click to collapse
You can try restore the backup with a recover

I had the same problem , flashing lineageos seems to fix it but you can never downgrade below android 10 again and keep baseband. You're stuck with using 10+ only unless you don't care about IMEI/baseband but yeah just flash the newest lineage and if that doesn't work flash the second to newest etc. Worked for me several times

In my case with Sprint xt1789-03 help this way:
Flash NASH_RETAIL_9.0_PPX29.159-24 with MotoFlashPro WHITHOUT modem section - UNCHECK this:
%fastboot% flash dsp adspso.bin
%fastboot% flash modem NON-HLOS.bin
%fastboot% flash fsg fsg.mbn
%fastboot% flash bluetooth BTFM.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
Then flash full latest sprit 8 android stock

PrivyetCyka said:
I had the same problem , flashing lineageos seems to fix it but you can never downgrade below android 10 again and keep baseband. You're stuck with using 10+ only unless you don't care about IMEI/baseband but yeah just flash the newest lineage and if that doesn't work flash the second to newest etc. Worked for me several times
Click to expand...
Click to collapse
That worked for my Device too. I had lost IMEI & baseband. First I flashed the latest TMO(04) image (you can use Lenovo/Motorola Rescue and Smart Assistant Software for Windows ) to get the baseband working and then flash LineageOS.