Database Users

Phone is Bricked. ADB won't recognize device on Windows 10.

I do not have a custom recovery. Can however boot to regular recovery. Tried to use ADB but computer just won't recognize the device. Tried multiple different cables.

vu45 said:
I do not have a custom recovery. Can however boot to regular recovery. Tried to use ADB but computer just won't recognize the device. Tried multiple different cables.
Click to expand...
Click to collapse
Can you tell us more about what's going and how you got to that point? And what device specifically?
What are you trying to do with ADB? It is really of no use at this point, can you access fastboot in the bootloader?

Tried to return to stock for update. Afterwards it just doesn't boot. X Pure 1575.
Trying to ADB into some sort of usable rom. It goes into ADB but computer won't recognize. Phone doesn't even boot into an OS.

vu45 said:
Tried to return to stock for update. Afterwards it just doesn't boot. X Pure 1575.
Trying to ADB into some sort of usable rom. It goes into ADB but computer won't recognize. Phone doesn't even boot into an OS.
Click to expand...
Click to collapse
ADB only works after the OS is booted... Do you have a terminal capture of your flash attempt? And how long are you waiting on first boot, it can take 30 minutes for first boot sometimes.

I do not unfortunately but it doesn't even boot into OS. It boots immediately into bootloader.

vu45 said:
I do not unfortunately but it doesn't even boot into OS. It boots immediately into bootloader.
Click to expand...
Click to collapse
Connect into bootloader mode to pc.
In cmd type+enter:
fastboot devices
/If you will see SN continue/
fastboot getvar all
/Copy and paste here the answer from pc/
If no devices:
Reinstall drivers + minimal adb & fastboot & repeat steps.
/Uninstall all drivers and programs for android, reboot pc, install/

(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Toshiba REV=07 PRV=00 TYPE=57 PNM=016G72
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA08403TSL
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 9362E5001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 358986064519224
(bootloader) meid:
(bootloader) date: 03-22-2016
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5: EDFE69452203DA0709C2C09BF656C85D
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Dec 8 16:59:17 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not available>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g94afac7 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:11:12 CST 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (142)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.062s

Continue in this state flashing stock rom. Here is how to:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Download xt1575.retus.24...18-8 from:
https://mirrors.lolinet.com/firmware/moto/clark/official/RETUS/ @vu45

Got it to boot! Thank you so much sir. If you don't mind me asking what does this mean:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Still got it to boot however
Also what is the latest security patch?

vu45 said:
Got it to boot! Thank you so much sir. If you don't mind me asking what does this mean:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Still got it to boot however
Also what is the latest security patch?
Click to expand...
Click to collapse
Those are related to devices that ship with Nougat, they have 2 software slots, basically fastboot is just telling you that there are not multiple slots found, which is true for this device, they are informational only.

acejavelin said:
Those are related to devices that ship with Nougat, they have 2 software slots, basically fastboot is just telling you that there are not multiple slots found, which is true for this device, they are informational only.
Click to expand...
Click to collapse
Ah thank you. I was wondering why it kept popping up.

vu45 said:
Ah thank you. I was wondering why it kept popping up.
Click to expand...
Click to collapse
Yeah, it seems pretty handy... my understanding is that Nougat devices and newer have 2 (or more) software slots, one is active and one is a backup, and you can even tell the device which one is active via fastboot... currently it is only used for seamless updates, although some custom ROMs may use this as well but I don't own a device that shipped with 7.0 or never so I haven't looked into it.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/

Alcatel 5065n ADB it won't recognize bricked phone
I have the drivers installed and it shows up Android device manager, but however when I type in command ADB devices the phone doesn't show up in the list

Lost IMEI Numbers XT1685

Hi I tried to flash this to stock (using POTTER_NPNS25.137-33-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) and now my IMEI numbers are lost. How do i get them back?

Can I request your get var info please, see what state your device is in?
To get the info:
Boot your device to bootloader.
Connect to your computer.
In the ADB terminal, type 'fastboot getvar all' without quotes. Press enter on your keyboard.
Copy paste the output here please. You may wish to remove your IMEI if present in the output.
Can I ask what firmware you had on your device before flashing the stock ROM, and where you got the ROM from? Have you tried flashing the non HLOS.bin and fsg.mbn partitions?

echo92 said:
Can I request your get var info please, see what state your device is in?
To get the info:
Boot your device to bootloader.
Connect to your computer.
In the ADB terminal, type 'fastboot getvar all' without quotes. Press enter on your keyboard.
Copy paste the output here please. You may wish to remove your IMEI if present in the output.
Can I ask what firmware you had on your device before flashing the stock ROM, and where you got the ROM from? Have you tried flashing the non HLOS.bin and fsg.mbn partitions?
Click to expand...
Click to collapse
I had Lineage OS on there and wanted to go back to stock and relock bootloader. So I followed the instructions to relock from here https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952 flashed everything, locking bootloader also worked and when i booted into the ROM everything was good except both IMEI were just "0" and i could not get network.
Anyway I have managed to solve it for now. I had a EFS backup on an SD Card. I unlocked bootloader again and restored the Lineage OS with the EFS partition and the IMEI are back! But I still don't know how to go back to stock. I guess for my model XT1685 there is no stock ROM? it seems I flashed the US ROM. For the first boot network worked but was 3G only and when I rebooted both my IMEI were lost.
Repeated the process and happened again!

syl0n said:
I had Lineage OS on there and wanted to go back to stock and relock bootloader. So I followed the instructions to relock from here https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952 flashed everything, locking bootloader also worked and when i booted into the ROM everything was good except both IMEI were just "0" and i could not get network.
Anyway I have managed to solve it for now. I had a EFS backup on an SD Card. I unlocked bootloader again and restored the Lineage OS with the EFS partition and the IMEI are back! But I still don't know how to go back to stock. I guess for my model XT1685 there is no stock ROM? it seems I flashed the US ROM. For the first boot network worked but was 3G only and when I rebooted both my IMEI were lost.
Repeated the process and happened again!
Click to expand...
Click to collapse
At least you got your device working again.
Hmm, the NPNS25.137-33-11 firmware should work for XT1685 retEU (and I imagine retGB too) devices. I would like to see your getvar info to confirm though. There's plenty of reports saying that NPNS25.137-33-11 is targeted towards retEU devices (e.g https://forum.xda-developers.com/g5-plus/how-to/update-npns25-137-33-11-august-2017-t3665211/page2)
Did you mean you flashed the US retail stock ROM before though? If so, losing IMEI/network access seems to be a common problem when switching between stock ROMs designed for different territories.
If you've flashed the US stock ROM before, you may have to look into flashing US specific ROMs e.g. NPN25.137-83, which should be the latest US ROM. However, as you've got an XT1685, you may no longer receive OTA updates, depending on what software channel your device reports.

echo92 said:
At least you got your device working again.
Hmm, the NPNS25.137-33-11 firmware should work for XT1685 retEU (and I imagine retGB too) devices. I would like to see your getvar info to confirm though. There's plenty of reports saying that NPNS25.137-33-11 is targeted towards retEU devices (e.g https://forum.xda-developers.com/g5-plus/how-to/update-npns25-137-33-11-august-2017-t3665211/page2)
Click to expand...
Click to collapse
Sorry about the delay. Didn't have access the device due to being away. Here is the getvar info:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: <Removed>
(bootloader) cid: 0x0032
(bootloader) channelid: 0x51
(bootloader) uid: EC9AF58100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: <Removed>
(bootloader) meid:
(bootloader) date: 08-30-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 3 3: 0:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.11.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.06u POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g64ca40a-0012
(bootloader) kernel.version[1]: 8-g77c6b6b ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Aug 8 08:37:28 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retapac
all: listed above
finished. total time: 0.127s
What ROM can i use to go back to stock, if at all possible?

syl0n said:
Sorry about the delay. Didn't have access the device due to being away. Here is the getvar info:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: <Removed>
(bootloader) cid: 0x0032
(bootloader) channelid: 0x51
(bootloader) uid: EC9AF58100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: <Removed>
(bootloader) meid:
(bootloader) date: 08-30-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 3 3: 0:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.11.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.06u POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g64ca40a-0012
(bootloader) kernel.version[1]: 8-g77c6b6b ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Aug 8 08:37:28 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retapac
all: listed above
finished. total time: 0.127s
What ROM can i use to go back to stock, if at all possible?
Click to expand...
Click to collapse
Thanks for the info, so it looks like your device still has NPNS25.137-33-11 (August 2017 security patch) on it.
However, the software channel of retapac gives me concern, as searching for Moto G5 Plus retapac firmwares seems to report that Moto G5 Plus XT1685 models for that channel are on a different firmware path compared to their retEU models.
At least one user, with a XT1685 on retapac, has reported being on the NPN25.137-15, then NPN25.137-67 and now NPN25.137-67-6 (August 2017) firmware. https://www.reddit.com/r/motog5/comments/6zqlkt/just_get_august_update_on_retapac_channel/
If that is the case, then that would be an explanation for the loss of IMEI when flashing the EU firmware, as your device is more in line with the Indian/Brazil firmware paths.
However, I'm having difficulty finding NPNS25.137-67-6 stock firmware, and given you have the August security patch, I do not recommend flashing the NPN25.137-15 (Jan 2017) firmware nor the NPN25.137-67 (March 2017) firmware, else if you take OTA updates you've got a high risk of hard bricking from the cross downgrading of firmware.
The only thing I can suggest is to perhaps wait for a newer retapac firmware than Aug 2017, depending on when/if it'll be leaked from Motorola. However, as I mentioned, cross flashing firmware is risky (as you've found out), so if you can, I'd probably avoid flashing stock firmware altogether. You may wish to look into the TWRP flashables which don't touch your bootloader: https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616

echo92 said:
Thanks for the info, so it looks like your device still has NPNS25.137-33-11 (August 2017 security patch) on it.
However, the software channel of retapac gives me concern, as searching for Moto G5 Plus retapac firmwares seems to report that Moto G5 Plus XT1685 models for that channel are on a different firmware path compared to their retEU models.
At least one user, with a XT1685 on retapac, has reported being on the NPN25.137-15, then NPN25.137-67 and now NPN25.137-67-6 (August 2017) firmware. https://www.reddit.com/r/motog5/comments/6zqlkt/just_get_august_update_on_retapac_channel/
If that is the case, then that would be an explanation for the loss of IMEI when flashing the EU firmware, as your device is more in line with the Indian/Brazil firmware paths.
However, I'm having difficulty finding NPNS25.137-67-6 stock firmware, and given you have the August security patch, I do not recommend flashing the NPN25.137-15 (Jan 2017) firmware nor the NPN25.137-67 (March 2017) firmware, else if you take OTA updates you've got a high risk of hard bricking from the cross downgrading of firmware.
The only thing I can suggest is to perhaps wait for a newer retapac firmware than Aug 2017, depending on when/if it'll be leaked from Motorola. However, as I mentioned, cross flashing firmware is risky (as you've found out), so if you can, I'd probably avoid flashing stock firmware altogether. You may wish to look into the TWRP flashables which don't touch your bootloader: https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
That is interesting. How do I have a UK charging brick on a retapac? Maybe its a Singapore model? I assumed it was GB as it had the UK plug.

Sorry for the inconvenience, I suffer a similar problem but when I use the command fastboot getvar all my imei and serial number appear, but when I start the device it says "imei 0"

same as here..did you find solution?

I have lost IMEI...below is getvar information..please help me which is correct firmware
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY223W45DX
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 165EDC7C00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358958060371611
(bootloader) meid:
(bootloader) date: 02-25-2017
(bootloader) sku: XT1686
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Dec 12 22:19:38 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.11.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.06u POTTER_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g64ca40a-0012
(bootloader) kernel.version[1]: 8-g77c6b6b ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Aug 8 08:37:28 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.040s

Try This
syl0n said:
Hi I tried to flash this to stock (using POTTER_NPNS25.137-33-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) and now my IMEI numbers are lost. How do i get them back?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808

Hi guys
can someone give me the EFS backup for XT1685 I Lost my IMEI numbers forever I can't get them again and I didn't backup before flashing a custom ROM. So I broke everything now ??

ayad.phonex said:
Hi guys
can someone give me the EFS backup for XT1685 I Lost my IMEI numbers forever I can't get them again and I didn't backup before flashing a custom ROM. So I broke everything now
Click to expand...
Click to collapse
Flashing someone else's EFS will not get your IMEI back. Also their EFS contains "their" info and should not be shared.

Cannot unlock relocked bootloader

The title says it all.
When i run the fastboot oem unlock <unique id> command,
it shows status 7 error.
cant get unlock data either. please help how do i unlock bootloader again

Have you booted the device into the operating system completely and gone into the Developer options re-enabled OEM Unlocking?
If that isn't it, unfortunately we have seen this in a small number of Moto devices (less than 1% I would say)... Once they are unlocked, then relocked, something happens and they can't be unlocked again. Sometimes after an OTA update is successfully applied they can be, but that isn't consistent either. Been an occasional problem with all retail Moto devices since the first Moto G & X models released in late 2013.
Out of curiosity... can you provide the output of "fastboot getvar all" and mask out your IMEI/MEID?

acejavelin said:
Have you booted the device into the operating system completely and gone into the Developer options re-enabled OEM Unlocking?
If that isn't it, unfortunately we have seen this in a small number of Moto devices (less than 1% I would say)... Once they are unlocked, then relocked, something happens and they can't be unlocked again. Sometimes after an OTA update is successfully applied they can be, but that isn't consistent either. Been an occasional problem with all retail Moto devices since the first Moto G & X models released in late 2013.
Out of curiosity... can you provide the output of "fastboot getvar all" and mask out your IMEI/MEID?
Click to expand...
Click to collapse
Yes, OEM Unlocking is enabled!
Damn, this is a very unlucky case I guess. I can't get my IMEI numbers up, and hence no SIM detection for me. I relocked the bootloader and gave it in for repairs at Moto, they said they won't cover it under warranty and quoted 80% of G5+'s retail price to install a new motherboard and get it fixed. So, I thought I would flash Pixel Experience 8.1 and flash stock modem as suggested by others, so tried to unlock it, and can't seem to get it unlocked. Meanwhile I have tried flashing stock fastboot files, but can't get IMEI to return. Is there any other solution?
Output of getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8C
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2242HSP4
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 80FBE67800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *removed*
(bootloader) meid:
(bootloader) date: 03-19-2017
(bootloader) sku: XT1686
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Nov 9 8:33: 2 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-92/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.281.9.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47u POTTER_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4524a37 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT M
(bootloader) kernel.version[3]: on Nov 20 09:32:29 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8C-0-g22013cf
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8C-0-gcba6d5d
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.047s

Same issue
Hi brother, I have the same problem which you were facing. Please suggest me some solution for this kind of issue if you had solved with your device. I did not find any solution till now feeling sad ..Kindly help me bro..
Thanks

Could be worse, mine is greyed out no matter what I fastboot. I tried my original firmware for my EU device and all the way up to the latest, always grayed out. You win Lenovo, I quit messing with my android devices after this one, this device has been a total mess. All my issues began with 64bit Roms.

Cupcake 1.5 said:
Could be worse, mine is greyed out no matter what I fastboot. I tried my original firmware for my EU device and all the way up to the latest, always grayed out. You win Lenovo, I quit messing with my android devices after this one, this device has been a total mess. All my issues began with 64bit Roms.
Click to expand...
Click to collapse
I have fixed devices in a worse situation than this. But this truly beats an enthusiastic child out of me. Well done Lenovo indeed! I think Lenovo Service Center blocks the unlock key once submitted for repairing for which they ask 75% of the cost.

SIM not found after flash stock 7.0

Hi.
I have flashed my moto x style mt1572 single sim using this guide:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
and this stock rom:
XT1572_CLARK_RETLA_DS_7.0_NPHS25.200-15-8_cid12_subsidy-DEFAULT_CFC.xml.zip
after flashing complete i get no sim slot detected. i was installed for dual sim device. then i installed the correct one:
XT1572_CLARK_RETLA_7.0_NPH25.200-15_cid12_subsidy-DEFAULT_CFC.xml.zip
i dont know what is the correct model for my device, but since there is just 2 stock firmware with android 7.0 and i was have this version in my OTA update, so i think this is the correct ROM.
but after installing this one, i got same problem. my baseband not found and IMEI is unknown.
i tried many solution that i found but doesnt work.
Did it fix if i flash a custom ROM??
sorry for my english.
thanks.

help me
any one can help me please????

One thing I discovered when tinkering with randomblame's LineageOS build is that when I flashed the Android 7 ROM on my Moto X Pure the modem did not properly install despite fastboot reporting success in flashing. I had to repeat flash it some five or six times before the SIM would be correctly detected as a GSM SIM so I could set the APN. I would try flashing the correct baseband for your device again, but repeatedly flash it as I did for the Moto X I have here.

Strephon Alkhalikoi said:
One thing I discovered when tinkering with randomblame's LineageOS build is that when I flashed the Android 7 ROM on my Moto X Pure the modem did not properly install despite fastboot reporting success in flashing. I had to repeat flash it some five or six times before the SIM would be correctly detected as a GSM SIM so I could set the APN. I would try flashing the correct baseband for your device again, but repeatedly flash it as I did for the Moto X I have here.
Click to expand...
Click to collapse
Hi.
thanks for your solution.
i am in trying fix it in last 3 days and i cant.
first i want to be sure that the ROM that i flashed is the correct one.
base on i was received the android 7.0 before and i have XT1572 single SIM, is it possible that the mentioned ROM is incorrect??
i have flashed LineageOS 14.1 but it freeze on logo and i can't try it. but i don't guess my problem fix by it at all.
OK now, your solution is that i flash my modem several times after i flashed the stock ROM?? this is mean that i repeat these commands ?? or just the (*) one?
Code:
fastboot flash modem NON-HLOS.bin *
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
edit:
this is my fastboot getvar all if it helps!
Code:
PS C:\Users\Yasser\Desktop> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA39101VSV
(bootloader) cid: 0x0007
(bootloader) channelid: 0x42
(bootloader) uid: 52C1EA001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358951060751668
(bootloader) meid:
(bootloader) date: 02-03-2016
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 11 21:18:11 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retla/clark:7.0/NPH
(bootloader) ro.build.fingerprint[1]: 25.200-15/14:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.15.clark_retla
(bootloader) ro.build.version.full[1]: .retla.en.01
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g6ed6ce8-0000
(bootloader) kernel.version[1]: 4-gfc58252 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed May 10 09:12:54 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=2d08904-dirty
(bootloader) hyp.git: git=2d08904-dirty
(bootloader) sdi.git: git=d9f358f
(bootloader) pmic.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) aboot.git: git=MBM-NG-VA0.52-0-g69ca042
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retfr
edit2:
i always receive this message after each command: (bootloader) has-slot:modem: not found
like below:
Code:
PS F:\rom> fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
Sending 'modem' (41723 KB) OKAY [ 0.924s]
Writing 'modem' OKAY [ 1.103s]
Finished. Total time: 2.040s
is this normal ??
thanks.

yasser93 said:
i always receive this message after each command: (bootloader) has-slot:modem: not found
like below:
is this normal ??
Click to expand...
Click to collapse
Slot not found errors are normal. Current versions of fastboot are designed for devices with seamless updates, and the Moto X doesn't have them.
Repeat flashing the modem means just the command "fastboot flash modem NON-HLOS.bin". You don't want to erase the partitions at all in doing this. Flashing the FSG is also not necessary.

Strephon Alkhalikoi said:
Slot not found errors are normal. Current versions of fastboot are designed for devices with seamless updates, and the Moto X doesn't have them.
Repeat flashing the modem means just the command "fastboot flash modem NON-HLOS.bin". You don't want to erase the partitions at all in doing this. Flashing the FSG is also not necessary.
Click to expand...
Click to collapse
I do it several times but nothing happens. is any other solution is exist???
thanks

yasser93 said:
I do it several times but nothing happens. is any other solution is exist???
Click to expand...
Click to collapse
Contact Lenovo.

Strephon Alkhalikoi said:
Contact Lenovo.
Click to expand...
Click to collapse
I do not know if i could share this link, but this is their answer
https://forums.lenovo.com/t5/Moto-X-Pure-Moto-X-Style/SIM-not-found-after-flash-stock-7-0/td-p/4404682

I don't see why sharing the link wouldn't be allowed. Nevertheless, the forums was not what I meant when I said to contact Lenovo. At this point the phone will likely need servicing at a Lenovo service center, and with the phone out of warranty that is something you have to pay for.

Finally Solved!!
i can't believe it. While I was completely disappointed, it fixed by simply flash this modem:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
:victory::victory::victory::victory::fingers-crossed::fingers-crossed::fingers-crossed::laugh::laugh:

hi there,
i have the same problem. my sister Huawei y9 prime is locked and she is no longer with us
what can i do to unlock it?
this is my email: [email protected]
help appreciated,

IMEI and Baseband unknown

I installed the ROM LineageOS 17.1 on my xt1962-4(Moto G7) and now my phone is without IMEI and without Baseband
And I'm not able to activate the SIM slot
TWRP:twrp-3.3.1-2-river
Rom used:lineage-17.1-20200423-nightly-river-signed
https://textsaver.flap.tv/lists/3d82

GamingHero said:
I installed the ROM LineageOS 17.1 on my xt1962-4(Moto G7) and now my phone is without IMEI and without Baseband
And I'm not able to activate the SIM slot
TWRP:twrp-3.3.1-2-river
Rom used:lineage-17.1-20200423-nightly-river-signed
https://textsaver.flap.tv/lists/3d82
Click to expand...
Click to collapse
Download the stock firmware
And flash
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Run
Code:
fastboot getvar all
To find codename ad software channel
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Find firmware @ https://mirrors.lolinet.com/firmware/moto
Sent from my Moto E (4) using Tapatalk

So did you ever figure it out? Having the same problem here, have tried many variations on the instructions above. Nothing I flash for either "RETAIL" or "RETUS" gives me my IMEI back. I've tried several full roms and also firmware only and then lineage.
What even constitutes the "stock firmware" for this device? XT1962-1 is supposed to be RETAIL, but it also says RETUS in several places. RETUS is supposed to be for XT1962-4 is it not? What is the true "stock firmware" for "Model: XT1962-1 Type: M0314"? That's what's inscribed on the back of the phone, but I've been doing
fastboot getvar all
< waiting for any device >
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-0ff2029-200211
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY2272SL7W
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: CCFC076500000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [redacted but present]
(bootloader) meid:
(bootloader) date: 11-29-2019
(bootloader) sku: XT1962-1
(bootloader) carrier_sku: XT1962-1
(bootloader) battid: SB18C34004
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 16 13:29:47 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/river/river:9/PPO29.114-1
(bootloader) ro.build.fingerprint[1]: 6/35c0:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.21.20.river.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld87) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version[2]: erelease) (GCC) ) #1 SMP PREEMPT Wed Jan
(bootloader) kernel.version[3]: 16 07:47:50 CST 2019
(bootloader) sbl1.git: MBM-2.1-river_retail-516ad1c-200211
(bootloader) rpm.git: MBM-2.1-river_retail-22daab3-200211
(bootloader) tz.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) devcfg.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) keymaster.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) cmnlib.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) cmnlib64.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) prov.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) aboot.git: MBM-2.1-river_retail-0ff2029-200211
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.011s
Click to expand...
Click to collapse
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Till I'm blue in the face and it does nothing. I also tried the Lenovo recovery thing on Windows, and it said the device isn't supported (?!)

If you made a backup of your persist partition, flash it with twrp. I haven't had to do it with the g7, but it always worked with the g5+.

Yeah I almost made a disclaimer like "and of course if I had a backup I'd flash that" but thank you.
---------- Post added at 03:38 AM ---------- Previous post was at 03:31 AM ----------
For the record, I figured my issue out. Had to flash XT1962-1_RIVER_RETUS_9.0_PPOS29.114-134-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

nothing yet, I even took it for technical assistance and nothing solves
does anyone have a suggestion? in addition to the possible motherboard exchange

Stumbled into a product desc. with some band nfo...dunno if it'll help but here it is....
http://phonedb.net/index.php?m=devi...l_sim_td-lte_in_64gb_xt1962-6__motorola_river

https://forum.xda-developers.com/g5-plus/how-to
We went through this with the G5+, and it boils down to a permissions issue in the persist partition. This guide should help, even though it is a different variant.