I'm trying to unlock the bootloader on my G7 Plus, however when I put the bootloader code into Motorola's website it tells me the device isn't compatible. I've talked to support 2 times now, once online and once over the phone, and they both have informed me that I have the Motorola G7 Plus, not the T-Mobile variant, and that the device can be unlocked. But when I put the code in on the website it just spins for a few minutes then says the device isn't supported.
I've run the getvar command and it says:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-201120
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZF6523R926
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 23A7CCF6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) sku: XT1965-T
(bootloader) carrier_sku: XT1965-T
Is there anything I can do?
Drinkingpants74 said:
I'm trying to unlock the bootloader on my G7 Plus, however when I put the bootloader code into Motorola's website it tells me the device isn't compatible. I've talked to support 2 times now, once online and once over the phone, and they both have informed me that I have the Motorola G7 Plus, not the T-Mobile variant, and that the device can be unlocked. But when I put the code in on the website it just spins for a few minutes then says the device isn't supported.
I've run the getvar command and it says:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-201120
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZF6523R926
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 23A7CCF6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) sku: XT1965-T
(bootloader) carrier_sku: XT1965-T
Is there anything I can do?
Click to expand...
Click to collapse
The moto unlock site is unreliable and finicky try a different
browser, pc, internet source...
or try later it often just doesn't work
sd_shadow said:
The moto unlock site is unreliable and finicky try a different
browser, pc, internet source...
or try later it often just doesn't work
Click to expand...
Click to collapse
I've tried on both a Linux and Windows laptop as well as my phone, on WiFi and on Data, all over a span of 7 hours, and none of them have worked. I'm beginning to think I might not be able to actually unlock the device.
When I look up the model number it tells me it's the T-Mobile one that isn't unlockable, but then I have a chat from Motorola telling me it's an official one. I might look for a different model of this device and see if it changes my outcome
Drinkingpants74 said:
I've tried on both a Linux and Windows laptop as well as my phone, on WiFi and on Data, all over a span of 7 hours, and none of them have worked. I'm beginning to think I might not be able to actually unlock the device.
When I look up the model number it tells me it's the T-Mobile one that isn't unlockable, but then I have a chat from Motorola telling me it's an official one. I might look for a different model of this device and see if it changes my outcome
Click to expand...
Click to collapse
Another option if you want to
PM me the unlock code and I can try it.
sd_shadow said:
Another option if you want to
PM me the unlock code and I can try it.
Click to expand...
Click to collapse
I've sent it if you're willing to give it a try. Thanks for this.
Drinkingpants74 said:
I've sent it if you're willing to give it a try. Thanks for this.
Click to expand...
Click to collapse
Sorry no luck here either.
Don't know why, your cid # should be available for unlock.
sd_shadow said:
Sorry no luck here either.
Don't know why, your cid # should be available for unlock.
Click to expand...
Click to collapse
I decided to give it another try today and for some reason it worked. I guess I just needed to be a lot more patient. Thanks for the help.
Drinkingpants74 said:
I decided to give it another try today and for some reason it worked. I guess I just needed to be a lot more patient. Thanks for the help.
Click to expand...
Click to collapse
Like I said site is finicky, and instead of it saying I'm sorry there's an error, it just says
"Your device does not qualify for bootloader unlocking."
it is strange that i got the same phone from amazon and i have unlocked it and installed custom rom successfully.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-201120
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZF6523****
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: D21D134B
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) date: 11-05-2020
(bootloader) sku: XT1965-T
(bootloader) carrier_sku: XT1965-T
youzi0335 said:
it is strange that i got the same phone from amazon and i have unlocked it and installed custom rom successfully.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-201120
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZF6523****
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: D21D134B
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) date: 11-05-2020
(bootloader) sku: XT1965-T
(bootloader) carrier_sku: XT1965-T
Click to expand...
Click to collapse
He got it unlocked, moto site was just not working correctly, and had to try several times.
Expert here, please help. I have moto g7 plus i got from Motorola directly as replacement variant (XT1965-T) but its going on boot loop. I tried to use Moto recover tool but it does read phone to do rom install. I tried manual also still not working. I tried to do install myself rom by using info and rom from another forum (https://motostockrom.com/motorola-moto-g7-plus-xt1965-t) but it fails to write using flasfile.bat. even though it says usb connected. in recovery mode it also shows OEM locked. is that's the reason ? I just want this phone to work with standard rom of it suppose to work as i got it unlocked version. Please help.
Related
Hi there everyone. This post of a question is going to be long. So, bear with me. A week ago I decided I wanted to unlock and root my Motorola E5 Play that I have been using with Consumer Cellular as the carrier for nearly a year. I have done this once before with my previous Android phone, so, naturally, I follow instructions to be found on websites, including those to be found on xda forums. The process did not go as expected. I installed the right Moto drivers on my laptop, installed adb utilities, got the Motorola unlock code via a portal to be found here on xda, and proceeded with the typical process. I can't remember all of the frustrations I had, but, basically, I ended up flashing the stock ROM for my phone just to get it usable again, and then discovered I had lost radio transceiver capabilities. I could not connect to Consumer Cellular's network to make or receive calls. The little icon for your cell signal strength was gone. I did a little reading on flashing necessary firmware for your phone's radio transceiver, but since I could find nothing about Consumer Cellular and the idea of going by specifications for my model phone and figuring it out without specific instructions seemed too much, I ultimately decided to buy a carrier unlocked model of my phone, take out the sim-card from my old phone and put it into the new phone. The new phone (or renewed should I say) was the exact same model of Moto E5 Play I had, it worked on the GSM networks, and so I have a working phone again. The only little problem was that, originally, the phone I just bought was an AT&T phone. So, I see the AT&T logo when I turn the phone on, and there are a couple of other quirks here and there, but once I backed up Android data to this phone from Google's Cloud everything was back. However, I still would like the benefits of a rooted smartphone, whether it be programs like SDMaid Pro having more access to clean your phone deeper, or being able to uninstall bloatware, customize boot up animations, etc.
So, after having screwed up as I did, I thought it might be best to pay a professional to unlock and root this newly bought renewed phone of mine. I tried making use of oneclickroot.com, but the operator there told me my phone is not eligible for OEM unlocking. This leads me to two requests of you guys here at xda. One of which may get this thread removed, and the other of which hopefully will be satisfied if this thread is not taken down due to the first request.
Request #1:
-------------------------
I know these phones are made with the capability of being unlocked. If it is not eligible for unlocking then it has something to do with the carrier. I know this because my previous phone (a Verizon Prepaid) was not eligible for unlocking when I got it years ago, but a nice and entrepreneurial Motorola employee looking to make a little money on the side over in China was gracious enough to email me the unlock code once I sent him $45 dollars via Paypal. So, if any of you know how to get my Consumer Cellular Moto E5 Play XT-1921-2 unlock code, be it this way, that way, or the other way, then, please, do tell.
Request #2:
--------------------------
I need some good instructions for unlocking and rooting this phone without screwing it up like I did the last one. If this involves extra steps like flashing needed firmware for the chipset the radio transceiver uses that is OK (I believe this model phone uses QualComm). I just need those steps spelled out and listed.
So, the grand goal here is an unlocked and rooted Motorola Android phone of mine. Relevant device information is below.
Model: Motorola E5 Play XT-1921-2
OS: Android 8.0.0 Oreo
Network: GSM
Carrier: Consumer Cellular
Radio Transceiver Chipset: Some version of QualComm
Baseband version: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
Build Number: OCPS27.91-157-15
Any help would be greatly appreciated.
***This question was originally posted by me in the general discussion area of xda forums for unlocking and not here like I was told should have been by a guy that replied to the question. I have reposted it here, and below I am including what he requested of me when the executing of the command "fastboot getvar all". The information returned by that command should be of help to whomever can assist me.***
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 9
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY323GTQV8
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 854514E600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359542090844190
(bootloader) meid:
(bootloader) date: 11-23-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: 6798BB
(bootloader) battid:
(bootloader) iccid: 89014103271819071604
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-157-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.16.james_a.a.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb838762-0007
(bootloader) kernel.version[1]: 1-g3aa9cf9 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 12 02:30:49 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=083cf5f-dirty
(bootloader) devcfg.git: git=083cf5f-dirty
(bootloader) keymaster.git: git=083cf5f
(bootloader) cmnlib.git: git=083cf5f
(bootloader) cmnlib64.git: git=083cf5f
(bootloader) prov.git: git=083cf5f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.396s
vindy1099 said:
Hi there everyone. This post of a question is going to be long. So, bear with me. A week ago I decided I wanted to unlock and root my Motorola E5 Play that I have been using with Consumer Cellular as the carrier for nearly a year. I have done this once before with my previous Android phone, so, naturally, I follow instructions to be found on websites, including those to be found on xda forums. The process did not go as expected. I installed the right Moto drivers on my laptop, installed adb utilities, got the Motorola unlock code via a portal to be found here on xda, and proceeded with the typical process. I can't remember all of the frustrations I had, but, basically, I ended up flashing the stock ROM for my phone just to get it usable again, and then discovered I had lost radio transceiver capabilities. I could not connect to Consumer Cellular's network to make or receive calls. The little icon for your cell signal strength was gone. I did a little reading on flashing necessary firmware for your phone's radio transceiver, but since I could find nothing about Consumer Cellular and the idea of going by specifications for my model phone and figuring it out without specific instructions seemed too much, I ultimately decided to buy a carrier unlocked model of my phone, take out the sim-card from my old phone and put it into the new phone. The new phone (or renewed should I say) was the exact same model of Moto E5 Play I had, it worked on the GSM networks, and so I have a working phone again. The only little problem was that, originally, the phone I just bought was an AT&T phone. So, I see the AT&T logo when I turn the phone on, and there are a couple of other quirks here and there, but once I backed up Android data to this phone from Google's Cloud everything was back. However, I still would like the benefits of a rooted smartphone, whether it be programs like SDMaid Pro having more access to clean your phone deeper, or being able to uninstall bloatware, customize boot up animations, etc.
So, after having screwed up as I did, I thought it might be best to pay a professional to unlock and root this newly bought renewed phone of mine. I tried making use of oneclickroot.com, but the operator there told me my phone is not eligible for OEM unlocking. This leads me to two requests of you guys here at xda. One of which may get this thread removed, and the other of which hopefully will be satisfied if this thread is not taken down due to the first request.
Request #1:
-------------------------
I know these phones are made with the capability of being unlocked. If it is not eligible for unlocking then it has something to do with the carrier. I know this because my previous phone (a Verizon Prepaid) was not eligible for unlocking when I got it years ago, but a nice and entrepreneurial Motorola employee looking to make a little money on the side over in China was gracious enough to email me the unlock code once I sent him $45 dollars via Paypal. So, if any of you know how to get my Consumer Cellular Moto E5 Play XT-1921-2 unlock code, be it this way, that way, or the other way, then, please, do tell.
Request #2:
--------------------------
I need some good instructions for unlocking and rooting this phone without screwing it up like I did the last one. If this involves extra steps like flashing needed firmware for the chipset the radio transceiver uses that is OK (I believe this model phone uses QualComm). I just need those steps spelled out and listed.
So, the grand goal here is an unlocked and rooted Motorola Android phone of mine. Relevant device information is below.
Model: Motorola E5 Play XT-1921-2
OS: Android 8.0.0 Oreo
Network: GSM
Carrier: Consumer Cellular
Radio Transceiver Chipset: Some version of QualComm
Baseband version: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
Build Number: OCPS27.91-157-15
Any help would be greatly appreciated.
***This question was originally posted by me in the general discussion area of xda forums for unlocking and not here like I was told should have been by a guy that replied to the question. I have reposted it here, and below I am including what he requested of me when the executing of the command "fastboot getvar all". The information returned by that command should be of help to whomever can assist me.***
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 9
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY323GTQV8
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 854514E600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359542090844190
(bootloader) meid:
(bootloader) date: 11-23-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: 6798BB
(bootloader) battid:
(bootloader) iccid: 89014103271819071604
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-157-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.16.james_a.a.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb838762-0007
(bootloader) kernel.version[1]: 1-g3aa9cf9 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 12 02:30:49 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=083cf5f-dirty
(bootloader) devcfg.git: git=083cf5f-dirty
(bootloader) keymaster.git: git=083cf5f
(bootloader) cmnlib.git: git=083cf5f
(bootloader) cmnlib64.git: git=083cf5f
(bootloader) prov.git: git=083cf5f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.396s
Click to expand...
Click to collapse
First I would try LMSA's Flash Rescue option with device in fastboot mode.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB 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: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s
hamhaingaurav said:
I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB 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: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s
Click to expand...
Click to collapse
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.
riyan65 said:
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.
Click to expand...
Click to collapse
Yes, I knwo there is an hope if i can unlock the bootloader, but the service center guy messed my device, I do not know how they flashed my device, they were flashing my device and said it is not turning on, i said okay return my device, i will flash it my self and after taking from them, i was trying to unlock the bootloader and I was getting the error "Code validation failure with status 7". I am also unable to get Unlock data.
What can i do now, is there any solution to it. Do i need to take my device to service center again ???
Try flashing april stock....then do the OTA update till August..
vivek1310yadav said:
Try flashing april stock....then do the OTA update till August..
Click to expand...
Click to collapse
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.
hamhaingaurav said:
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.
Click to expand...
Click to collapse
PM me..
Just got phone yesterday from amazon. In my attempts to do so fastboot has either "froze" with 3 dots, nothing, or errors like unknown command and a couple others. Ive done this before with previous moto phones. Used moto instructions and other guides and no luck. So any help is appreciated.
g422 said:
Just got phone yesterday from amazon. In my attempts to do so fastboot has either "froze" with 3 dots, nothing, or errors like unknown command and a couple others. Ive done this before with previous moto phones. Used moto instructions and other guides and no luck. So any help is appreciated.
Click to expand...
Click to collapse
what does getvar all say
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200929
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZF6523S7H9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
sd_shadow said:
what does getvar all say
Code:
fastboot getvar all
Click to expand...
Click to collapse
g422 said:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200929
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZF6523S7H9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
Click to expand...
Click to collapse
Cid should be good (bootloader) cid: 0x0032
There should have been several more lines of data?
Try updating adb files
sd_shadow said:
Cid should be good (bootloader) cid: 0x0032
There should have been several more lines of data?
Try updating adb files
Click to expand...
Click to collapse
Have latest platform tools now the
fastboot getvar is stuck where it labels cpu
g422 said:
Have latest platform tools now the
fastboot getvar is stuck where it labels cpu
Click to expand...
Click to collapse
Try rebooting pc and change usb ports
g422 said:
Have latest platform tools now the
fastboot getvar is stuck where it labels cpu
Click to expand...
Click to collapse
It just gave me the serial no under cpu so she is just slow as hell im gonna let it go for awhile see it gives more info than before
sd_shadow said:
Try rebooting pc and change usb ports
Click to expand...
Click to collapse
Okay so i restarted used different usb port and different usb plug.
Fastboot getvar showed me what i posted but is hung and has been for 20 mins.
i'm the same one and just finished unlock, first had the same problem with you.
my solution is change to another computer.
your pc has compatibility issues with the phone.
just started with my dell laptop G7, when move to tower 5810 it is ok.
unlock/flash recovery/install rom, there are always issues appears on the laptop, but it never shown on the desktop.
youzi0335 said:
i'm the same one and just finished unlock, first had the same problem with you.
my solution is change to another computer.
your pc has compatibility issues with the phone.
just started with my dell laptop G7, when move to tower 5810 it is ok.
unlock/flash recovery/install rom, there are always issues appears on the laptop, but it never shown on the desktop.
Click to expand...
Click to collapse
Yeah thats what im thinking as well. Im just glad to know it is unlockable. Looks like i have to rebuild my old pc.
When I run fastboot oem get_unlock_data, nothing appears on the screen. Typing fastboot getvar all prints this:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190920
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SKHYNIX LP4x DIE=12Gb M5=06 M6=04 M7=00 M8=0D
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224WTJN6
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 7CD622B2
The cid would be cid: 0x0000 to be unlockable?
I run fastboot getvar ro.carrier and it's ro.carrier: reteu.
Any help or advice?
Any relation with this?
'' For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange ''
I checked through adb and my phone is set to '' 1'' and ''green''.
All the others settings are appropriate for unlocking.
Source:
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
Finally, I used a Macbook and I fixed it. The problem probably happened by the drivers of ADB.
Two days ago I got my hands on a "mint" XT1925-6, and I'm still waiting for OEM Unlock to be un-grayed (available) in Dev Options.
I've nearly lost count of the number of Moto phones I've owned, rooted, bootloader-unlocked in the past 5-6 years. I've never had to wait more than one quick little WiFi connection before tapping OEM unlock.
I know this phone is unlockable because I've already got its unlock code, emailed to me straight from Motorola. So that question has been asked and answered. But I'm still waiting to be able to tap and enable OEM Unlock.
I found the verbage below in the Lenovo G6/Plus/Play support forum -- https://forums.lenovo.com/t5/Moto-G...lay-software-image/m-p/5077477?page=1#5317655
This question was asked concerning a G6 Play (XT1922), but I've also found this same answer for the XT1925 in other pages that I've since lost track of . . . to wit, how does one get the phone unlocked if the OEM bootloader unlock switch is greyed out.
Answer by 'Agent Rich' in the 2nd post (MY emphasis/caps/etc): "I've seen it before, it looks like the phone needs to have an active data connection for a WEEK for the OEM option [to] become available."
And then in the 4th post (the last one): "The phone needs to have an active data [connection] to help mitigate the risk of device being stolen and re-flashed."
". . . . . . to help mitigate the risk of device being stolen and re-flashed" . . . . . What kind of B.S. answer is that?
Does anybody have any kind of meaningful response to this horse****?
In the meantime I've disabled all the google junk and other useless stuff while keeping the phone on an "active data connection" (WiFi), in the (probably vain) hope that it won't be anywhere near a week before OEM gets enabled . . . . . . . . . . . . . .
Firmware version is PPS29.118-15-11-16; 'getvar all' shows CID 0x0032. Just to be sure, and despite the 'advice' from 'Agent Rich', is there anything else I can look at that might show the phone I have is not a genuine, official, carrier-unlocked/bootloader-unlockable XT1925-6?
NINE days and still waiting for OEM Unlocking to enable.
The phone IS unlockable according to Motorola. I've got the unlock code. XT1925-6, RetUS, CID 0x0032, everything says it's unlockable. Methinks something is fishy with this phone but I have no idea what. No clue at all.
--- fastboot getvar all (from "day 1" after an FDR) ---
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: [**********]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: AC94058600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [***************]
(bootloader) meid:
(bootloader) date: 05-03-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jul 25 14:56: 2 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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
I might try reflashing the firmware I downloaded through the Rescue program. Or maybe run an actual rescue through that software.
Moondroid said:
I might try reflashing the firmware I downloaded through the Rescue program. Or maybe run an actual rescue through that software.
Click to expand...
Click to collapse
The invalid slots are concerning.
I would reflash the firmware, then reconnect to the internet.
sd_shadow said:
The invalid slots are concerning.
I would reflash the firmware, then reconnect to the internet.
Click to expand...
Click to collapse
I see what you mean. I reflashed last night but didn't think to run getvar and compare. I just did that, again after reflashing FW downloaded through Lenovo Rescue and Smart Assistant, and those slots still show invalid . . .
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: [**********]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: AC94058600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [***************]
(bootloader) meid:
(bootloader) date: 05-03-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 4 17:30: 0 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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
Another thing: On this phone OEM Unlocking shows completely grayed out. But on another G6 (XT1925-6) that I picked up cheap in an eBay auction, the OEM Unlocking verbage is not grayed out. Just the button.
Edit/Add: Identical phones, exact same firmware. The second phone also shows those slots as Invalid.
getvar all from the second phone (the one that shows only the button disabled). I'm still looking for any differences . . .
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: ********DJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: FA6FB84D00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: *************19
(bootloader) meid:
(bootloader) date: 10-28-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Sep 13 12: 0:16 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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
PS: This getvar all is before I corrected the time to current.
Clarification on the images: The first image is from the second phone. The second image is from phone #1, the one I've had for 10 days and reflashed yesterday. I just double-checked on the phones themselves.
Phone #1 (100% gray):
emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5
Phone #2 (button only gray):
emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01
After taking a relaxing 4-day vacation I remembered a possible solution, which worked on the #2 phone (haven't tried it on #1):
-- FDR
-- Setup as new with Wireless enabled. I did this with Wifi turned on but without an actual working Internet connection. Apparently it just wants WiFi enabled.
-- Setting the date may or may not matter. I just went through the setup using "Skip" and "Next" liberally.
-- Enabled Developer Options and Presto, OEM Unlock was enabled. My previously requested Unlock Code then worked to unlock the bootloader.
I'm experiencing this exact same issue. The phone is a Motorola Edge 30 Neo XT2245-1. I just opened the product package, turned it on, used the Motorola website to request the bootloader unlock code (which I received via email, no problem), and then I found out that the "OEM unlock" checkbox in Android Settings > Developer options is shown but it's grayed out. It is completely grayed out, meaning both the text and the checkbox are grayed out. What I did afterwards was search XDA and found a couple of threads, most of them suggesting to do a factory reset (via the Android settings), which I did, but that didn't help.
I'm hoping now that it's simply a timer, and that I have to wait a few days before the checkbox starts working. The CID value is 50 (or hex 0x32), and I already received the bootloader unlock code, so I'm pretty sure it should be possible to liberate this phone without having to resort to (or waiting for new) privilege escalation exploits.
Will post in a few days whether it (the "OEM unlock" setting) becomes toggle-able. Feel free to nudge me if I forget to do so.
heisenbug#3141 said:
I'm experiencing this exact same issue. The phone is a Motorola Edge 30 Neo XT2245-1. . . .
Click to expand...
Click to collapse
2-3 weeks ago I went through this again with a Motorola One 5G Ace. I waited 8 days with nothing changing, finally tried a factory reset and voila. Unlock enabled.
There no longer seems to be any predictable method to this madness. Good luck, you'll get there eventually.
Moondroid said:
2-3 weeks ago I went through this again with a Motorola One 5G Ace. I waited 8 days with nothing changing, finally tried a factory reset and voila. Unlock enabled.
There no longer seems to be any predictable method to this madness. Good luck, you'll get there eventually.
Click to expand...
Click to collapse
That's wicked. Based on that, I guess it might be that, whether or not the "OEM unlock" will be toggle-able is decided at the time of the reset, or soon after the first successful internet connection has been established, and that this result is saved. In other words, the option perhaps won't become toggle-able afterwards. If that's true, it might even work to just simply try a factory reset every single day until it's toggle-able, because one of those days the (server-side) timer has elapsed. Or, if that theory proves to be false, then perhaps you need to wait at least N days and do a factory reset after having waited long enough. Time will tell. Anyhow, thanks for shining light on this! Really hoping for the best here.
It's unlocked now. The "OEM unlock" option became toggle-able today. It seems waiting is all you have to do after requesting the bootloader unlock code via the Motorola website.
For future reference, and for anyone stumbling upon this here:
I did the last factory reset about 4 days ago and from that moment on I just waited and checked every day whether the "OEM unlock" option was toggle-able or not. And when it was, I toggled it, heeded the well-known warnings, and used 'fastboot' to unlock it. I had the device a few days longer, so in total I waited about a week before being able to unlock it.
Also, in case anyone wonders, whether or not a SIM card is inserted should not matter if one's phone is an international (global) model, as those aren't carrier locked. My phone is an international model and the SIM card was not inserted while waiting for the "OEM unlock".
Whispering digits of pi to the phone also apparently doesn't matter.