So I just got one of these off my friend and I'm trying to get it up and running. I can't currently get past boot. If I let it go it boot loops, if I boot into recovery it boot loops... if I do anything other than "Boot loader logs", QR Codes or Restart bootloader it bootloops. I've spent the last 2 hours trying to find a solution around but I'm not finding anything close to what I need. I've tried the return to stock tool in the development section. It gets a bunch of errors when it's trying to flash stuff (Remote Failures). I can post that code if needed. I can get into fastboot but nowhere past it. I think the problem may stem from me having a locked bootloader (it's unable to be unlocked, already tried that on Moto's site). Is there any way I can unbrick this thing?
EDIT: Had formatting wrong on the unlock code. it is eligible. Waiting on the code now.
EDIT 2: Can't unlock because Allow OEM Unlock isn't on in dev options... but I can't get to dev options since I can't get into the OS... -.-
EDIT 3: Reading around it seems like I SHOULD be able to flash stock firmware even with a locked bootloader so long as it passes preflash verification. I've downloaded 18-8, 18-4 and 18_cid7 from here: https://androidfilehost.com/?a=show&w=files&flid=44735 which is where the official Motorola builds are hosted. None of them have passed preflash verification.
here's my getvar all
(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: 32GB Toshiba REV=07 PRV=00 TYPE=57 PNM=032G72
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA394001K4
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 0782A0001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355486060585298
(bootloader) meid:
(bootloader) date: 09-10-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Dec 11 23:50: 4 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-8/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.8.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g2c916d9 (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 Fri Sep 23 04:48:05 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.48-0-g86c6f70
(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.48-0-g86c6f70
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.079s
Click to expand...
Click to collapse
Which, if I'm reading right says the current version is 18-8. Is it possibly due to carrier that it's not flashing?
Last Edit: Alright I give up. I've downloaded every one off the official page, over 7GB of images total. Not a single one passes pre-flash verification. This is so aggravating. If anyone could point me in SOME direction at all so I don't lose my mind I'd be forever greatful. I've filed for a warranty, fully expecting this to be unfixable. Will be sending it Monday.
This is your version:
(bootloader) ro.build.version.full[0]:Blur_Version.24.221.8.clark_retus
You have to wait for it or Nougat(flashable).
With locked BL you cannot do anything except warranty repair.
@TraMaI
Ps.
Retus - cid9 is for you.
So basically I have to wait for a version they haven't put out yet? How long does it usually take for them to post them?
Use the retus 18-8 version, do not flash bootloader.img or gpt.bin but continue through everything else.
Will probably bootloop first time, boot into recovery (after flashing it) and perform a factory reset, then reboot and give it a minimum 20 minutes.
BTW, Factory Reset Protection is active "(bootloader) frp-state: protected (75)", so you will need the last Google account used on that device to access it... otherwise it's a brick.
Hello,
I have a big problem, my fingerprint and dual sim is not working anymore on stock. The device detects my phone as a G4 not G4 Plus.
I have tried many firmwares but it all seems to make no difference.
Code:
(bootloader) version: 0.5(bootloader) version-bootloader: moto-msm8952-B1.03
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2239QDL4
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: A420B70000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354117070969310
(bootloader) meid:
(bootloader) date: 06-13-2016
(bootloader) sku: XT1642
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 6 20:20:45 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-48/48:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.31.48.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband: M8952_70030.25.03.62R ATHENE_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g06a4fb5 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld35) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Sun Jun 5 11:16:49 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB1.03-0-ge433b40
(bootloader) rpm.git: git=MBM-NG-VB1.03-0-ga970ead
(bootloader) tz.git: git=MBM-NG-VB1.03-0-g119e5b2
(bootloader) hyp.git: git=MBM-NG-VB1.03-0-g119e5b2
(bootloader) keymaster.git: git=MBM-NG-VB1.03-0-g119e5b2
(bootloader) cmnlib.git: git=MBM-NG-VB1.03-0-g119e5b2
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (142)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.088s
Press any key to continue . . .
No solution that works has been found yet. It pretty much has always boiled down to a trip to the service center.
Same issue here but with an xt1644. I got this after trying to reflash stock N running the same fastboot script that I originally upgraded to nougat on. Reverted to stock M, restored TWRP backups - no success - so it doesn't seem software related - at least not on any of the partitions that successfully flash. gpt.bin gives errors when trying to flash downgrade as does the bootloader so maybe it is related to these partitions if it is software. The march security update messes with the bootloader I believe.
If anyone has taken their phone to a service center, was there any indication on what they do to fix it? codGmer - what did you do just before this issue appeared?
I've tried to get back to stock and didn't know about flashing gpt.bin and bootloader.img could break the system. So I flashed those and after that my device wouldn't boot anymore and after I got it working again my fingerprint function was gone.
I just send my phone out to repair where I bought it. I have bricked my bootloader with some qualcom tool so the phone wouldn't boot anymore just flashing light to fake the device being broken by faulty hardware. Also the Costs of returning unrepaired to me will be paid for me.
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.
C:\adb>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.102s]
finished. total time: 0.103s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2238RLPB
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 074B980000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-28-2016
(bootloader) sku: XT1643
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 22 1:25:41 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.02R ATHENE_INDIA_
(bootloader) version-baseband[1]: DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-ge03508d-00131-g44
(bootloader) kernel.version[1]: 2576f ([email protected]) (gcc version
(bootloader) kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version[3]: :58:16 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.129s
Did you find a solution to this situation? I have the same problem ...
j_cesarbm said:
Did you find a solution to this situation? I have the same problem ...
Click to expand...
Click to collapse
I have same issue and Moto Service has refused to help.
If I am not mistaken, this is defect in OEM firmware, which is reason why they may be having issues with Oreo 8.1 upgrade. Someone at Moto has no keys for OEM boot loader. Earlier Alphadog would help, but now he says contact customer service.
Waiting to see if my assumption is correct. So far Oreo 8.1 OTA not received. Motorola web site also says it will no more receive security patches.
mang0sings said:
I have same issue and Moto Service has refused to help.
If I am not mistaken, this is defect in OEM firmware, which is reason why they may be having issues with Oreo 8.1 upgrade. Someone at Moto has no keys for OEM boot loader. Earlier Alphadog would help, but now he says contact customer service.
Waiting to see if my assumption is correct. So far Oreo 8.1 OTA not received. Motorola web site also says it will no more receive security patches.
Click to expand...
Click to collapse
How has Motorola service failed to help? They couldn't generate a code for you? It's possible that only a motherboard repair or replacement can fix the bootloader unlock problem, especially if there are parameters missing from the getvar info.
Our device is over 2 years old, and for our device was only slated to get 2 major updates and 2 years of security patches. Do you have an active SIM card in your device?
I gave up trying to fix it, sold it, and bought another.
echo92 said:
How has Motorola service failed to help? They couldn't generate a code for you? It's possible that only a motherboard repair or replacement can fix the bootloader unlock problem, especially if there are parameters missing from the getvar info.
Our device is over 2 years old, and for our device was only slated to get 2 major updates and 2 years of security patches. Do you have an active SIM card in your device?
Click to expand...
Click to collapse
I gave up trying to fix it, sold it, and bought another.
j_cesarbm said:
I gave up trying to fix it, sold it, and bought another.
Click to expand...
Click to collapse
That's the right decision. That could also be reason their Oreo update has failed miserably. No more security patches will be released.
My moto g4 play had hardbrick and I recovered it and it only lets me flash gpt bootloader logo fsg and modem the rest gives me error of preflash validation failed but even with gpt I get imei and serial no but I do not have cid since before brick this it damage with a bad flashing by adb shell dd if even with the brick I can enter qualcomm mode, flashing sbl1 with gpt.bin restart and the computer recognizes it attached my getvar all:
(bootloader) has-slotartition: not found
(bootloader) is-logicalartition: not found
Sending 'partition' (32 KB) OKAY [ 0.094s]
Writing 'partition' (bootloader) This may take a
few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.515s]
Finished. Total time: 0.780s
C:\Users\suwog>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-81.12(*)
(bootloader) product: harpia
(bootloader) board: harpia
(bootloader) secure: yes
(bootloader) hwrev: 0x81B0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=08 PRV=0D TYPE=57
(bootloader) ram: 2GB Samsung S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: ZY223RXJQW
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: 5A9D2C2100000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 268435456
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 354138073943532
(bootloader) meid:
(bootloader) date: 12-04-2016
(bootloader) sku: XT1601
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon May 28 8:28:15 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/harpia/harpia:7.1.1/NPIS2
(bootloader) ro.build.fingerprint[1]: 6.48-43-2/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.26.241.3.harpia.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.2.9-01810-8x16.0
(bootloader) version-baseband[0]: M8916_20250112.18.05.45.01R HARPIA_LAT
(bootloader) version-baseband[1]: AM_CUST
(bootloader) kernel.version[0]: Linux version 3.10.107-6.90-g853fd69-dir
(bootloader) kernel.version[1]: ty ([email protected]) (gcc version 7.1.1 20
(bootloader) kernel.version[2]: 170614 (crosstool-NG crosstool-ng-1.23.0
(bootloader) kernel.version[3]: -90-g81327dd9 - Linaro GCC 7.1-2017.07~d
(bootloader) kernel.version[4]: ev) ) #23 SMP PREEMPT Thu Jul 13 16:35:4
(bootloader) kernel.version[5]: 5 UTC 2017
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: git=MBM-NG-V81.12-0-g5f9a108
(bootloader) tz.git: git=MBM-NG-V81.12-0-gcf5b5ba
(bootloader) hyp.git: git=MBM-NG-V81.12-0-gcf5b5ba
(bootloader) aboot.git: git=MBM-NG-V81.12-0-gf9417da
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (75)
(bootloader) ro.carrier: tefmx
all: listed above