No IMEI after flashing the Stock from, Unable to Unlock the Bootloader - Moto G5S Plus Questions & Answers

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..

Related

Unlock bootloader moto x 2014 - XT1097

I recently bought this used cell phone, with android 5.1, I upgraded to the 6 stock (original motorola) but I now want to install a custom ROM, and for this I need to unlock the bootloader, but when I try to do this, this message appears in the command prompt "could Not get unlock data! ", I even tried a crazy on the internet some method to solve but what I found said that I should downgrade and go up rom, but I can not install another rom by RSD lite, I would like a method to be able Do the bootloader unlock and do root, exchange rom these things
roneyss93 said:
I recently bought this used cell phone, with android 5.1, I upgraded to the 6 stock (original motorola) but I now want to install a custom ROM, and for this I need to unlock the bootloader, but when I try to do this, this message appears in the command prompt "could Not get unlock data! ", I even tried a crazy on the internet some method to solve but what I found said that I should downgrade and go up rom, but I can not install another rom by RSD lite, I would like a method to be able Do the bootloader unlock and do root, exchange rom these things
Click to expand...
Click to collapse
You must have the unlock.bin from motorola official site to unlock bootloader.
After send the unlock.bin to your mail you move it to adb folder etc.
papsr6 said:
You must have the unlock.bin from motorola official site to unlock bootloader.
After send the unlock.bin to your mail you move it to adb folder etc.
Click to expand...
Click to collapse
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
roneyss93 said:
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
Click to expand...
Click to collapse
Did you enable Developer Options by going to Settings, About, tap Build Number 7 times, then go back, enable allow bootloader unlock and Android Debugging.
roneyss93 said:
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
Click to expand...
Click to collapse
Do it again you do something wrong.
I do the same and my fault is the wrong copy of numbers when i copy from commant window.
Gus Ghanem said:
Did you enable Developer Options by going to Settings, About, tap Build Number 7 times, then go back, enable allow bootloader unlock and Android Debugging.
Click to expand...
Click to collapse
I do exactly this, and it continues to give error
papsr6 said:
Do it again you do something wrong.
I do the same and my fault is the wrong copy of numbers when i copy from commant window.
Click to expand...
Click to collapse
I can not even get the numbers that we put on the Motorola site, I have unlocked Motorola before, however this nor give me the codes when I put the command to generate the codes
roneyss93 said:
I do exactly this, and it continues to give error
Click to expand...
Click to collapse
Do this just to get some info, no need to paste it here:
fastboot getvar all
In bootloader mode of course.
EDIT: You can get the latest fastboot and adb from here:
https://developer.android.com/studio/releases/platform-tools.html
Gus Ghanem said:
Do this just to get some info, no need to paste it here:
fastboot getvar all
In bootloader mode of course.
EDIT: You can get the latest fastboot and adb from here:
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Open again the CMD, the most updated according to the link that you sent me. And as a response the commands had this.
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: 6018
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: 0432146139
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: EC13870C0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 353320060936783
(bootloader) meid:
(bootloader) date: 2014-10-24
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jul 5 12:11:27 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retbr/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: br.retbr.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_S
(bootloader) version-baseband[1]: INGLELA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:44:51 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V60.18-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.18-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V60.18-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.18-0-g4ad5029
(bootloader) aboot.git: git=MBM-NG-V60.18-0-g3b3b501
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.229s
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot devices
0432146139 fastboot
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Could not get unlock data!
OKAY [ 0.036s]
finished. total time: 0.036s
D:\Programas\Celular\MOTO X 2\root\platform-tools>
Remember that yes "OEM unlock" and "USB debugging" was enabled. As shown in the image.
Here is mine
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x000E
(bootloader) channelid: 0x80
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-12-2015
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 1 15:55:30 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retca/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: ca.retca.en.CA
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_R
(bootloader) version-baseband[1]: ETCA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:53:00 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: retca
Looks like your bootloader is older, but it shouldn't matter, I think I unlocked mine before the Android 6.0 update, I then relocked it, and unlocked it again a second time. I'm sure a lot of RETBR phones have been unlocked around here. I just can't see what the problem is. But don't try downgrading, you may brick the phone. I don't know what else to suggest. I'm sure you've installed the Motorola USB drivers, but I don't think that's the issue.
Try the Motorola (Lenovo) forums, you can submit your getvar to them, and they will send you an unlock code in a few days:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
Good Luck!
They have forums in Portugese.
Gus Ghanem said:
Here is mine
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x000E
(bootloader) channelid: 0x80
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-12-2015
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 1 15:55:30 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retca/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: ca.retca.en.CA
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_R
(bootloader) version-baseband[1]: ETCA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:53:00 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: retca
Looks like your bootloader is older, but it shouldn't matter, I think I unlocked mine before the Android 6.0 update, I then relocked it, and unlocked it again a second time. I'm sure a lot of RETBR phones have been unlocked around here. I just can't see what the problem is. But don't try downgrading, you may brick the phone. I don't know what else to suggest. I'm sure you've installed the Motorola USB drivers, but I don't think that's the issue.
Click to expand...
Click to collapse
I also do not know what the problem, I even tried to do the downgrade but does not accept any other android pq is not unlocked the bootloader.

My XT1063 goes "failed to validate boot image"

I am stuck in the AP Fastboot Flash Mode (S). Recovery, Factory, BP Tools doesn't function, giving the same line "failed to validate xxx image". I can't flash stock ROMs through fastboot commands, all of those were "Failed". The bootloader lock can't even be unlocked, same reason above. Anybody from XDA can help me with this? I desperately tried almost everything on the forum and nothing has progressed so far. Here is the getvar-all information of my device:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4887
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D325JTJ
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: AAED95070F000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359297055872880
(bootloader) meid:
(bootloader) date: 01-21-2015
(bootloader) sku: XT1063
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Nov 1 4:11:27 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 6.0/MPBS24.65-34-4/6:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.4.titan_retug
(bootloader) ro.build.version.full[1]: lb.retuglb.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8626BP_1032.3116.99.00R RETUSA_GLB_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g495dfd8 ([email protected]
(bootloader) kernel.version[1]: ilclbld36) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Wed Aug 24 07:20:10 CDT 2016
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V48.87-0-g1b80345
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe:
(bootloader) productid:
(bootloader) sutinfo:
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 34.876s
I would really appreciate if somebody can solve this problem for me.
Hi! Sorry if im late, but did you use a 1 click flash tool? I reflashed 5.0.2 on my 1063 but i used a 6.0 flash tool and i got the same error! It got corrected once i used the correct flash tool
Angel064able said:
Hi! Sorry if im late, but did you use a 1 click flash tool? I reflashed 5.0.2 on my 1063 but i used a 6.0 flash tool and i got the same error! It got corrected once i used the correct flash tool
Click to expand...
Click to collapse
I used mfastboot and manually entered the codes. Where can I get that flashtool?
imnewbieplsnokick said:
I used mfastboot and manually entered the codes. Where can I get that flashtool?
Click to expand...
Click to collapse
I used this video:youtu.be/Jav4tIv5sCI
Credit to the creator.
Did you downgraded the ROM of your device? The one which comes out of the box? The chances are this happens when you flash downgraded Stock flash files on upgraded bootloader. Try flashing latest factory image available for your device and firstly re flash partition, boot, recovery and bootloader files. Then go for all other flash files serially. This solution 'might' help. Otherwise there's nothing you can do.
imnewbieplsnokick said:
I used mfastboot and manually entered the codes. Where can I get that flashtool?
Click to expand...
Click to collapse
Did you solved your issue? My device went to the same state while I was trying to relock the bootloader and re-unlocking it fixed it!
Angel064able said:
Did you solved your issue? My device went to the same state while I was trying to relock the bootloader and re-unlocking it fixed it!
Click to expand...
Click to collapse
Sorry, I was quite busy with my mid-semester. I tried it out and it didn't work. I guess it is dead now. However, I am thinking about breaking the phone, turning it into a hard-brick state and then reincarnate it back to life. Is it possible?

Moto X4 - Payton XT1900-2 - fastboot working, adb not working - OEM_Locked - Help

Dear Members,
My friend Have Moto X4 (Out of Warranty) this phone popup always says "Close App". So he cannot use the phone.
We tried to repair the phone 2-3 shops. No one able to solve the issue.
I am new to Android, So I thought to watch some youtube videos and downgrade the OS.
So I tried to reduce the Android version to "PAYTON_RETAIL_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
My bad, I watched only some Youtube videos (munchy) and started the procedure from that video.
After those steps My phone Locked. I tried to get help from him but he says the following.
"your bootloader is locked ..nothing i can do to help". sorry.
I have product vairiant : payton XT1900-2 64GB P4.
Power ok, then "oem_locked".
I am using Windows 10.
Some more information
--------
C:\adb>fastboot devices
ZY224GVR4R fastboot
--------
Fastboot recognize the device. adb not working. I have the Unlock Code from Motorola. But I cannot use it.
C:\adb>fastboot oem unlock WDEJJDCG2WPXNSWBGRT7
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
mobile network not detected.
Tried with Wi-fi, the device search progress bar keeps on running. Didn't find the Hotspots/Wifi Router. There is no next button to proceed.
please advise me the next step. Thanks for the reply and your help.
I have the logs while the first attempt fails and erase everything.
Please help to use the phone. Thanks
patrickjjs said:
Dear Members,
My friend Have Moto X4 (Out of Warranty) this phone popup always says "Close App". So he cannot use the phone.
We tried to repair the phone 2-3 shops. No one able to solve the issue.
I am new to Android, So I thought to watch some youtube videos and downgrade the OS.
So I tried to reduce the Android version to "PAYTON_RETAIL_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
My bad, I watched only some Youtube videos (munchy) and started the procedure from that video.
After those steps My phone Locked. I tried to get help from him but he says the following.
"your bootloader is locked ..nothing i can do to help". sorry.
I have product vairiant : payton XT1900-2 64GB P4.
Power ok, then "oem_locked".
I am using Windows 10.
Some more information
--------
C:\adb>fastboot devices
ZY224GVR4R fastboot
--------
Fastboot recognize the device. adb not working. I have the Unlock Code from Motorola. But I cannot use it.
C:\adb>fastboot oem unlock WDEJJDCG2WPXNSWBGRT7
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
mobile network not detected.
Tried with Wi-fi, the device search progress bar keeps on running. Didn't find the Hotspots/Wifi Router. There is no next button to proceed.
please advise me the next step. Thanks for the reply and your help.
I have the logs while the first attempt fails and erase everything.
Please help to use the phone. Thanks
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
Please post it here, and remove IMEI line
Sent from my Moto E (4) using Tapatalk
Thanks Shadow
sd_shadow said:
Run
Code:
fastboot getvar all
Please post it here, and remove IMEI line
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (0)
(bootloader) serialno: ZY224GVR4R
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: A1A80AC4
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: ---------------
(bootloader) meid:
(bootloader) date: 12-16-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4270
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (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]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190409
(bootloader) git:tz: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:hyp: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:devcfg: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:keymaster: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) gitrov: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:storsec: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retin
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.176s
C:\adb>
patrickjjs said:
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (0)
(bootloader) serialno: ZY224GVR4R
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: A1A80AC4
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: ---------------
(bootloader) meid:
(bootloader) date: 12-16-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4270
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (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]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190409
(bootloader) git:tz: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:hyp: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:devcfg: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:keymaster: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) gitrov: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:storsec: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retin
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.176s
C:\adb>
Click to expand...
Click to collapse
You cannot unlocked the bootloader unless
Oem unlock is allowed in dev options
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Help through remote screen
sd_shadow said:
You cannot unlocked the bootloader unless
Oem unlock is allowed in dev options
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi Shadow, Can you help through Team viewer or Anydesk, if possible.
Thanks
Process device information screen
patrickjjs said:
Hi Shadow, Can you help through Team viewer or Anydesk, if possible.
Thanks
Click to expand...
Click to collapse
Hi Shadow,
It pops up "Process device information screen " for more than 10 mins. It never returned anything.
Progress bar going on and going on.....
Tested with two times with Admin mode.
Any ideas.
Thanks
hello, could you solve your problem, for my adb if it works, that's why it returns the serial number in the command window, I think you are only trying to flash the wrong firmware, since it is not necessary to have the bootloader unlocked to flash via adb, you have to download a firmware xt1900-2 retail, regards
Solved?
patrickjjs said:
Hi Shadow,
It pops up "Process device information screen " for more than 10 mins. It never returned anything.
Progress bar going on and going on.....
Tested with two times with Admin mode.
Any ideas.
Thanks
Click to expand...
Click to collapse
Did you ever got it working? i'm probably on the same Scenario, tried a lot of stuff, but no sucess.

Bootloader relock Moto e4 plus

Hi, I turn to this forum as a last hope, I have a Motorola Moto e4 Plus xt1776, resulting that I lost some important files and wanted to try to recover them, in short, I try to root the phone, but I could not, I only activate the fastboot following the steps from of a forum.
When I had the fastboot activated, note that the boot logo had changed and lotrate to change, but in the end it got a horrible one, after I saw that some applications like netflix no longer grabbed them, and I decided to block it again thinking that everything would return to how it was Before, it locks the bootloader and it turns out that now I have my phone with a horrible startup logo, without my important files and I also cannot download my netflix which clearly before if I could, I don't know what could be worse (At least the phone works) . I need your help, please download a motor tool for the pc called rescue and smart assistant, but I don't know if that will help me to have it as I had before doing everything.
Without more to say thank you very much, I would really appreciate it, if you help me put it as it was before, with its original logo and everything as it was when I bought it, he could never install the TWRP, never go beyond that.
I believe that the phone believes that it still has the bootloader unlocked, but this is impossible as it allows me to enable and disable the OEM option.
PS: when I start the bootloader, an image of the green android would come out, now a white square comes out, here I leave the information that the adb gives me:
:\Users\Gastón\Downlo
fastboot devices
Y224B52HP fastbo
C:\Users\Gastón\Downloads\Motorola\platform-tools_r30.0.1-windows\platform-tools
>fastboot oem device info
(bootloader) 'device' is not
a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
fastboot: error: Command failed
C:\Users\Gastón\Downloads\Motorola\platform-tools_r30.0.1-windows\platform-tools
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-BD.41
(bootloader) product: owens
(bootloader) board: owens
(bootloader) secure: yes
(bootloader) hwrev: P3A
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY224B52HP
(bootloader) cid: 0x0032
(bootloader) channelid: 0x86
(bootloader) uid: BD529D6C00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 256691592100280583
(bootloader) meid:
(bootloader) date: 08-25-2017
(bootloader) sku: XT1776
(bootloader) battid:
(bootloader) iccid: 89011202000051822440
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/owens_sprint/owens:7.1.1/
(bootloader) ro.build.fingerprint[1]: NCRS26.58-44-25/32:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.301.32.owens_spri
(bootloader) ro.build.version.full[1]: nt.sprint.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8920_02.02.06.79.06R OWENS_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g8087b62 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Wed Aug 14 18:44:37 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VBD.41-0-gf35bf13
(bootloader) rpm.git: git=aa33522-dirty
(bootloader) tz.git: git=d9e7085-dirty
(bootloader) devcfg.git: git=d9e7085-dirty
(bootloader) keymaster.git: git=d9e7085-dirty
(bootloader) cmnlib.git: git=d9e7085-dirty
(bootloader) cmnlib64.git: git=d9e7085-dirty
(bootloader) prov.git: git=d9e7085-dirty
(bootloader) aboot.git: git=MBM-NG-VBD.41-0-ge117241
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: sprint
all: listed above
Finished. Total time: 0.268s

[SOLVED] Now no OEM Unlock for 7 days???

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.

Categories

Resources