My Wife has an X4, xt1900-1 from Google Fi, that she no longer uses as a phone but uses it on wifi only to run a special piece of software. It got the "device is corrupted" error and will not boot to anything other than FastBoot. Adding results of "Fastboot getvar all" at the end of post. Running "Fastboot oem get_unlock_data" returns:
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
Finished. Total time: 0.003s
Running LMSA initially wouldn't detect the device, then it did detect and begins the re-flash process but fails at flashing around 69 percent.(nice) No other information is given other than flashing failed.
Attempting to flash the firmware that the LMSA downloaded manually via fastboot and it flashes the first couple bits but fails at the bootloader.
Attempting to fastboot boot into twrp returns:
Sending 'boot.img' (38672 KB) OKAY [ 1.412s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
I found the blankflash image for this version of payton, when attempting to run it, the terminal just displays:
< waiting for device >
And nothing ever happens.
I've tried it on Windows and Linux with a handful of different cables and the results are the same. Am I SOL and it's time to replace the device?
Thanks,
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(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 (2)
(bootloader) serialno: ZY224H58SP
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 356484080483981
(bootloader) meid:
(bootloader) date: 10-15-2017
(bootloader) sku: XT1900-1
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3899
(bootloader) iccid: 8901260971113779407
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton_fi/payton_sprout:9
(bootloader) ro.build.fingerprint[1]: /PPWS29.69-39-6-13/badd5:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.491.55.payton_fi.
(bootloader) ro.build.version.full[1]: google_fi.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7048.65.01.101R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g097f40be62ed
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.x
(bootloader) kernel.version[2]: 20150123 (prerelease) (GCC) ) #1 SMP PR
(bootloader) kernel.version[3]: EEMPT Thu Sep 24 04:43:29 CDT 2020
(bootloader) git:abl: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) git:xbl: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) gitmic: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) git:rpm: MBM-3.0-payton_fi-f97e5eb-200924
(bootloader) git:tz: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:hyp: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:devcfg: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib64: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:keymaster: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) gitrov: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:storsec: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(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: 4
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.047s
Heyyo, blankflash only works if you reboot the device into EDL mode. I can't remember if powering it off, holding down both volume keys and plugging it into a PC will actually boot it into EDL mode or not for Motorola devices though...
You can also try the TinyFastbootScript and see if that works?
Download the ROM from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Download TinyFastbootScript from here which also has the instructions:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work and you can't force reboot to EDL? You can search on Amazon / AliExpress or others for an "Android EDL cable" which can also work to force EDL mode.
ThE_MarD said:
Heyyo, blankflash only works if you reboot the device into EDL mode. I can't remember if powering it off, holding down both volume keys and plugging it into a PC will actually boot it into EDL mode or not for Motorola devices though...
You can also try the TinyFastbootScript and see if that works?
Download the ROM from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Download TinyFastbootScript from here which also has the instructions:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work and you can't force reboot to EDL? You can search on Amazon / AliExpress or others for an "Android EDL cable" which can also work to force EDL mode.
Click to expand...
Click to collapse
Awesome thanks for the reply. Yeah I tried a couple different key combinations that I have seen people reference but nothing seemed to work, however I didn't try holding down both volume keys while plugging it in. I'll try that, and also try the tinyfastboot script too and see what happens. Thanks!
Well I think it's toast. The Tinyfastboot script was giving a lot of the same errors when I was running things manually. I could not get the device to boot into EDL through key combinations either. I think the biggest issue is that the bootloader is locked, and cannot be unlocked. I might try to find a cable and give that a shot but I am thinking now it's a waste of time.
Thanks for the help anyway.
Im facing same issue here as well. so EDL method doesnt work?
Related
Hi all.
My phone bricked out of the blue, all stock, locked fastboot, no upgrades installed for quite some time, only Play Store apps installed.
It can't get past fastboot. When I try to Start Android, it shows "Failed to validate boot image. ERROR: failed to pass validation, backup to fastboot".
Same messages when I try to enter Recovery Mode.
Tried installing TWRP, but I can't get the fastboot unlock code, shows error message below:
C:\Program Files\Android\Android Studio>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.004s]
finished. total time: 0.004s
Baseband field is blank, and IMEI is 0.
Product/Variant is showing: hannah 000000000000000 16GB P3
ATM I have no need for custom roms, unlocks or anything like that, but if it's the way to go, I would go for it.
Any ideias on how to approach this?
Below I send all vars, if it helps somehow:
C:\Program Files\Android\Android Studio>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BE.4F(*)
(bootloader) product: hannah
(bootloader) board: hannah
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: d0f001b8
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 1ECC453900000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VBE.4F-0-g4e3d3ac
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.055s
What variant do u have
Pbsipher1 said:
What variant do u have
Click to expand...
Click to collapse
Thanks for your reply, and I apologize if I don't answer this correctly, I'm not very knowledgeable in these things...
I'm from Brazil, and bought it here, so doing some research, I found this:
OPP27.91-146 Brazil / XT1944-4
I don't know if there's any way to check it within fastboot as well... a lot of vars are blank at this moment...
The only other thing that looks like a variant here is: hannah
Lenovo Moto Smart Assistant
Try using the "Lenovo Moto Smart Assistant". After installing, connect your phone to your computer, open the program, click flash - rescue - and follow the instructions.
Ex novo said:
Try using the "Lenovo Moto Smart Assistant". After installing, connect your phone to your computer, open the program, click flash - rescue - and follow the instructions.
Click to expand...
Click to collapse
Just tried that, but no dice. Tried all variations of Moto E5, never got recognized.
"Failed to match the connected device. Please plug it out, and try again".
Tried plugging it out/in several times, but no luck.
Thank you for the suggestion, though.
Have the same problem. Could you fix it? Thx
Only hope is blankflash or possibly flashing newer stock firmware, its on telegram group
I seem to have the same issue.
Did you manage to find a way to fix this?
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.
Good morning friends! I have a problem that has become painful for me these past few days! I took my moto g7 xt1962-4 (river) and installed a PixelExperience recovery and a rom for this build.
Version: 10
File name: PixelExperience_river-10.0-20201123-1209-OFFICIAL.zip
MD5 hash: 4f9130df18136891e982baa925fc9bc6
Date: November 23, 2020 12:09 UTC
Downloads: 121
However after installing the recovery and finalizing the installation of the zip (ROM) my device restarted and remained on fastboot, I tried to use the minimal adb to repair the device, I tried to use rsd to repair the device, and I also used the tool lenovo repair, if anyone knows what is happening, thank you. Below I will leave the reading of getvar all.
(before installing the rom the bootloader was unlocked and now the oem_locked status)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-f238a87f119-201124
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 1056de9d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-f238a87f119-201124
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.113s
C:\Program Files (x86)\Minimal ADB and Fastboot>
João Pedro Cordeiro said:
Good morning friends! I have a problem that has become painful for me these past few days! I took my moto g7 xt1962-4 (river) and installed a PixelExperience recovery and a rom for this build.
Version: 10
File name: PixelExperience_river-10.0-20201123-1209-OFFICIAL.zip
MD5 hash: 4f9130df18136891e982baa925fc9bc6
Date: November 23, 2020 12:09 UTC
Downloads: 121
However after installing the recovery and finalizing the installation of the zip (ROM) my device restarted and remained on fastboot, I tried to use the minimal adb to repair the device, I tried to use rsd to repair the device, and I also used the tool lenovo repair, if anyone knows what is happening, thank you. Below I will leave the reading of getvar all.
(before installing the rom the bootloader was unlocked and now the oem_locked status)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-f238a87f119-201124
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 1056de9d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-f238a87f119-201124
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.113s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
When the bootloader changes from unlocked to lock by itself or after flashing a rom, only fix I've seen is.
Booting to EDL Mode
Try
Code:
fastboot oem blankflash
If you can boot a custom recovery like TWRP
see reboot options for EDL
or use
Code:
adb reboot edl
With twrp booted.
If device is in Emergency Download Mode (EDL Mode)
Screen will be black and will be shown as Qualcomm device on PC
i also faced this problem when i flash the lineageos, this is a low version bootloader and cannot turn to edl mode, i use TinyFastbootScript fix this issue.
get a stock rom and flash the BP/BL.
net time you'd better install the copy-partitions-20200903_1329.zip before flash a new custom rom.
I managed to get him to go to edl and use blankflash but still no ah how to install twrp or firware
I bought another plate for the device, I thank everyone on the forum for their attention, you are excellent people, and now we have a story about a brick
sd_shadow said:
When the bootloader changes from unlocked to lock by itself or after flashing a rom, only fix I've seen is.
Booting to EDL Mode
Try
Code:
fastboot oem blankflash
If you can boot a custom recovery like TWRP
see reboot options for EDL
or use
Code:
adb reboot edl
With twrp booted.
If device is in Emergency Download Mode (EDL Mode)
Screen will be black and will be shown as Qualcomm device on PC
Click to expand...
Click to collapse
everything worked fine on EDL but it still doesn't work, I can put it in qualcomm mode but I didn't succeed
João Pedro Cordeiro said:
everything worked fine on EDL but it still doesn't work, I can put it in qualcomm mode but I didn't succeed
Click to expand...
Click to collapse
you mean the phone can worked on EDL mode but you cannot use blankflash function?
blankflash - mirrors.lolinet.com > firmware > motorola > lake > blankflash
make sure the edl driver has been installed and check the 9008 mode shown in the device manager.
after the blankflash the phone can be set to bootloader mode, then you can do other trying.
Hello, please help !! My moto g7 plus ran out of recovery when I tried to put twrp on it. If I restart or turn off first, it enters the fastboot option and I have to press star to continue turning on. I already put stock firmware several times and it remains the same. Please someone to explain to me how I do the flashing so that the recovery stock returns. Thank you
Grislu said:
Hello, please help !! My moto g7 plus ran out of recovery when I tried to put twrp on it. If I restart or turn off first, it enters the fastboot option and I have to press star to continue turning on. I already put stock firmware several times and it remains the same. Please someone to explain to me how I do the flashing so that the recovery stock returns. Thank you
Click to expand...
Click to collapse
What does getvar all say? (remove imei before posting)
Code:
fastboot getvar all
edit:
Are you following the install method from this thread?
[RECOVERY] Official TWRP 3.3.1 for Moto G7 Plus [lake]
Team Win Recovery Project 3.x, or twrp for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
hi, i get this. Thank you
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZY2269JHHS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x0e
(bootloader) uid: C4AB995C
(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) imei:
(bootloader) meid:
(bootloader) date: 06-24-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 3897
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10
(bootloader) ro.build.fingerprint[1]: 1-21-18-7/fac4a:user/rele
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: M636_21.71.02.66R LAKE_LATAMDSDS
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ (no
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 2
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREE
(bootloader) kernel.version[3]: an 29 09:20:56 CST 2021
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-210129
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-210129
(bootloader) gitmic: MBM-3.0-lake_retail-efaf0cccb-210129
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-210129
(bootloader) git:tz: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:hyp: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:devcfg: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:cmnlib: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:keymaster: MBM-3.0-lake_retail-3da76fb4f-21012
(bootloader) gitrov: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:storsec: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tefco
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.203s
I have been using my Moto X4 on a custom ROM (with magisk) for over 3 years without any issues. Just yesterday, my phone battery died and I plugged in a charger and start up the phone in a couple of mins and I get this message "Your device is corrupt. It cant be trusted and will not boot.
I was surprised to find that on the Fastboot screen, the OEM Status shows as LOCKED - How can this happen after so many years and that too in a snap ?
The problem now is that I'm not sure if the "OEM Unlocking option" under Developer Settings is disabled (It has been long since I went into these settings).
When I try to unlock OEM, I get this message below. What are my options now since the phone doesn't start for me to enable the option using the GUI ? I would like to access my data if there is an chance.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock O4USDSC3JS6UX4VQBA1B
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-c18849c-181018
(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: ZY224GABCD
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351899081981234
(bootloader) meid:
(bootloader) date: 10-25-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4135
(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-3-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.306.16.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M660_7036.16.01.69.02R PAYTON_APACDSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gc27dd6c (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]: Thu Oct 18 11:53:59 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-c18849c-181018
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-181018
(bootloader) git:pmic: MBM-3.0-uefi-dfccc3a-181018
(bootloader) git:rpm: MBM-3.0-uefi-245b046-181018
(bootloader) git:tz: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:hyp: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:devcfg: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:cmnlib: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:cmnlib64: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:keymaster: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:prov: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:storsec: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retin
(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
finished. total time: 0.984s
C:\Program Files (x86)\Minimal ADB and Fastboot>
1/ You'd better hide serial and imei number from your post
2/ Moto forums say to try to fix it going back to stock rom using rescue software
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
And if does not work to send to repair services
GL
OK. I tried the RSA software and that too identifies my phone correctly, downloads the Stock ROM and failed with an error message saying "Flash Failed. try again". Could this be due to the settings in Developer options being disabled ?(which I cannot get to)
I tried the below to see if it helps, but didnt get far :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.514s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.524s
Do I have any options to bring back my phone even if if the data is lost and i need to go back to stock ROM or any other ROM. I just want to have a working phone. Please advise.
Is there a way to unlock the OEM or enable the Unlock OEM in Dev settings without being able to boot into the Operating system ?
Only if you can send adb commands
And so, be able to enter Recovery mode (buttons volume down+power when phone off, just in case)
'Install update > From adb' menus will make you enter adb mode
There may have plenty of softwares for data recovery through adb
Finway said:
Only if you can send adb commands
And so, be able to enter Recovery mode (buttons volume down+power when phone off, just in case)
'Install update > From adb' menus will make you enter adb mode
There may have plenty of softwares for data recovery through adb
Click to expand...
Click to collapse
Thanks. Can adb commands be used even if USB debugging may not be enabled ? Can you guide me to a post on the forum which I can use to follow instructions to try and install a new ROM keeping in mind my current situation.
In Recovery Mode yes you can send adb commands
Do you have acces to it ?
Code:
adb sideload lineage-19.1-20220426-nightly-payton-signed.zip
or any other version of lineage to install it
Info about payton | LineageOS Wiki
wiki.lineageos.org
may i know if this is solved? i have same problem as well, wanna know how to get my x4 out of the error message