Database Develop

Moto E2 XT1511 Bricked Bootloader Locked

Hi guys thanks for passing by... i have this issue with my phone and i need some info to see if i finally drop it or if i can do something by myself to get back my phone...
the issue is that when i woke up i found my phone on the black screen of the fastboot flash mode (s) whit this message *unable to validate system so i guess that i lost the system,
when i tried to get back to my system it went back to the fastboot screen, reading for a while i decided to flash back my phone but i have the Bootloader locked, knowing that i lost the firmware of the phone, info that read in some forums decided to ask you guys what can i do, thing is that i can't flash
*Logo
*Boot
*Bootloader
*Recovery
*System
Cant erase anything either cus if i do the factory reset sends me again to the fastboot flash mode again. tried to unlock the Bootloader with the code and it says "allow oem unlock" in developers option... so ya... im completely blocked up cus can't access to the phone so my question is there's something that i could do i got the tools like msfastboot fastboot adb and some others that it says that does something but none of them helped me .
attached: getvar all and the results of the flashing commands.
Thanks for any comment, recommendation, suggestion or any information that could get me out of doubt
Screen:
AP Fastboot Flash Mode (s)
51.0B(*) (sha-eddaefe, 2016-08-05 14:47:25)
product variant: otus xt1511 8gb p3
cpu: MSM8212 CS
eMMC 8gb Micron RV=06 PV=12 TY=17
DRAM 1024MB Elpida S4 SDRAM DIE=4GB
BATTERY OK
Device is LOCKED. status code:0
Connect USB Data Cable
Boot Mode Selection Menu
Vol Up Selects , Vol Dowm Scrolls
Normal Porwerup
Recovery
Factory
Barcodes
BP Tools
QCOM
failed to validate boot image
Fastboot Reason: Fall-through from not-charger boot mode
getvar all:
C:\Users\User>fastboot devices
TA107002WN fastboot
C:\Users\User>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 510B
(bootloader) product: otus
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x6
(bootloader) emmc: 8GB Micron REV=06 PRV=12 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8212 CS
(bootloader) serialno: TA107002WN
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 38DB7D0A12000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 299892736
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355451060286073
(bootloader) meid:
(bootloader) date: 02-24-2015
(bootloader) sku: XT1511
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Aug 23 2:56:10 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/otus_retuaws/otus:5.1/LPC
(bootloader) ro.build.fingerprint[1]: S23.13-56-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.201.5.otus_retuaw
(bootloader) ro.build.version.full[1]: s.retuaws.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]: MSM8610BP_18033.4614.46.00R RETUSA_AWS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g57926e4 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Sat Sep 10 01:10:50 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-V51.0B-0-geddaefe
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe:
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 34.927s

[SOLVED]moto XT1900-4 flashing locked and can't unlock

Hi, i own a moto x4 since early 2018 and had no problems with unlocking the bootloader, then installing twrp and then root with magisk...
The problem is I was getting bored about a notification that says that there was a new update for my phone and it always failed when i try to download and install it, so i tried to fix it. I really don't know developing but i thought the problem was related to the "your device can't be checked for corruption" notification that i got everytime y booted my phone. So I thought "Man, i just have to lock the bootloader again" and maybe I'll successful install that update.
Well, things don't go well when I typed the command "fastboot oem lock" on cmd, I saved a security copy of my things before typing the command for the second time. Then i tried rebooting the phone and get that ugly red notification...
It says "Your device is corrupt. It can't be trusted and will not boot". Okay I tried the exact same method I did when unlocked the bootloader for the first time but don't work. So I don't know how to proceed.
Anybody can help me? Thanks for reading
Code:
PS C:\Users\-bich\Desktop\platform-tools_r28.0.0-windows\platform-tools> .\fastboot oem unlock YMCVIWY57PMTFM7EKO56
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
Code:
.\fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180530
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY224WWDP8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x28
(bootloader) uid: C1F34D0A
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356486081345556
(bootloader) meid:
(bootloader) date: 03-23-2018
(bootloader) sku: XT1900-4
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4274
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-17/23:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.271.23.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M660_7036.16.01.69R PAYTON_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g8a19f40 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed May 30 14:43:30 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180530
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180530
(bootloader) git:pmic: MBM-3.0-uefi-dfccc3a-180530
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180530
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:prov: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: opencl
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above

VicenteCL said:
Hi, i own a moto x4 since early 2018 and had no problems with unlocking the bootloader, then installing twrp and then root with magisk...
The problem is I was getting bored about a notification that says that there was a new update for my phone and it always failed when i try to download and install it, so i tried to fix it. I really don't know developing but i thought the problem was related to the "your device can't be checked for corruption" notification that i got everytime y booted my phone. So I thought "Man, i just have to lock the bootloader again" and maybe I'll successful install that update.
Well, things don't go well when I typed the command "fastboot oem lock" on cmd, I saved a security copy of my things before typing the command for the second time. Then i tried rebooting the phone and get that ugly red notification...
It says "Your device is corrupt. It can't be trusted and will not boot". Okay I tried the exact same method I did when unlocked the bootloader for the first time but don't work. So I don't know how to proceed.
Anybody can help me? Thanks for reading
Code:
PS C:\Users\-bich\Desktop\platform-tools_r28.0.0-windows\platform-tools> .\fastboot oem unlock YMCVIWY57PMTFM7EKO56
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
Code:
.\fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180530
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY224WWDP8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x28
(bootloader) uid: C1F34D0A
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356486081345556
(bootloader) meid:
(bootloader) date: 03-23-2018
(bootloader) sku: XT1900-4
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4274
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-17/23:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.271.23.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M660_7036.16.01.69R PAYTON_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g8a19f40 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed May 30 14:43:30 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180530
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180530
(bootloader) git:pmic: MBM-3.0-uefi-dfccc3a-180530
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180530
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:prov: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: opencl
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Click to expand...
Click to collapse
is you phone booting in system?
If yes: Enter in Developer Settings an activate "Enable OEM Unlocking" -- No have this option??? Enable ADB, and enable superuser by ADB.
And run: adb shell setprop ro.oem_unlock_supported 1
Now "Enable OEM Unlocking" activated option showing!!! Enable it and re-run "fastboot oem unlock code"!
If your system not booting:
Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in your phone! And repeat steps above!

juniofdm said:
is you phone booting in system?
If yes: Enter in Developer Settings an activate "Enable OEM Unlocking" -- No have this option??? Enable ADB, and enable superuser by ADB.
And run: adb shell setprop ro.oem_unlock_supported 1
Now "Enable OEM Unlocking" activated option showing!!! Enable it and re-run "fastboot oem unlock code"!
If your system not booting:
Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in your phone! And repeat steps above!
Click to expand...
Click to collapse
Worked with the second method! THANK YOU SO MUCH! It has come back to life!

Im getting this error error: device '(null)' not found

juniofdm said:
is you phone booting in system?
If yes: Enter in Developer Settings an activate "Enable OEM Unlocking" -- No have this option??? Enable ADB, and enable superuser by ADB.
And run: adb shell setprop ro.oem_unlock_supported 1
Now "Enable OEM Unlocking" activated option showing!!! Enable it and re-run "fastboot oem unlock code"!
Click to expand...
Click to collapse
Can you tell me or help me to enable superuser by ADB?

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

No IMEI after flashing the Stock from, Unable to Unlock the Bootloader

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

Bootloader Unlock Code XT1965-T (Not the T-Mobile version)

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.