Android not working, Can't unlock bootloader, Can't Factory Reset. Need Help - Motorola One Vision Questions & Answers

I have a Motorola One Vision XT1970-1 working strangely.
First, It wont get into the system. After powering on it shows the ANDROID ONE logo, short shake and then shorter shake. It stays on that screen for as long as I let it, hours even.
Second, holding volume down and power to start the device brings me to fastboot mode. It says battery is OK and the phone bootloader is locked.
At fastboot mode I can get some info like fastboot getvar all (full text below) but if I try to unlock it with fastbook oem unlock ***CODE I GOT FROM MOTOROLA*** it tells me I need to
"Allow OEM Unlock" in Android Settings > Developer"
Click to expand...
Click to collapse
but as I cannot go into the system I am stuck here.
I can see the current slot is "a" and if I try to change it with fastboot --set-active=b it tells me
"Command is not allowed".
Click to expand...
Click to collapse
Third, if I go to recovery mode I see a message before I do anything, at the bottom, saying
"E:Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: I/O error".
Click to expand...
Click to collapse
This message repeats if I try to "Wipe data/factory reset" or "Mount /system".
If I try to sideload I get, on the computer side, the message
"adb: failed to read command: Success"
Click to expand...
Click to collapse
and on the mobile side:
(adbd status 1)
Installation aborted.
E:Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: I/O error
Click to expand...
Click to collapse
Forth, I tryed to use a blank flash software but I could not make the mobile be recognized at the computer as a serial device. I shows up at Windows Device Manager as either a mobile phone or as a Linux storage device.
Any ideas to get it back working?
Bellow, the `fastboot getvar all` result
Spoiler: fastboot getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-4b580da-191115
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB WDC SDINDDH4-128G FV=1268
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: ***REDACTED***
(bootloader) cid: 0x0032
(bootloader) channelid: 0x09
(bootloader) uid: 000002D62FA9167A0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ***REDACTED***
(bootloader) meid:
(bootloader) date: 05-15-2019
(bootloader) sku: XT1970-1
(bootloader) carrier_sku: XT1970-1
(bootloader) battid: ***REDACTED***
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Apr 23 19:16:50 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/kane/kane_sprout:9/PSAS29
(bootloader) ro.build.fingerprint[1]: .160-55-7-1/23312:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.291.1.kane.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.samsung: 20190621
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2585551
(bootloader) kernel.version[0]: Linux version 4.14.56-gc3b443e (hudsoncm
(bootloader) kernel.version[1]: @ilclbld69) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (https://and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Fri Nov 15 08:36:18 CST 2019
(bootloader) bootloader.git: MBM-2.2-kane_retail-4b580da-191115
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: tefbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.609s

Related

HELP Saving data before hard reset with only recovery mode accessible

After updating by itself with almost empty battery (probably to Android 10) my device wont boot up anything except Fastboot and Recovery Mode. On this device I did not modify anything at all previously, no root, no custom bootloader no nothing. I did not even unlock developer options/usb debugging in the settings, which is probably what now haunts me. I know a factory reset will be an easy fix, but I would really like to recover at least some data first, which seems pretty impossible to do but im not just ready to give up.
I can get very limitied acces through ADB.
- If I choose "Apply update from ADB" in Recovery mode, my PC reconizes the device in the device-manager and I can choose drivers etc. But obvioulsly not view files in the explorer or anythng else helpful.
- The command "fastboot getvar all" works and spits out a huge list of variables about the phone
- The command "adb devices" displays a number and "sideload" when the option "Apply update from ADB" is selected in the Recovery, but nothing at all is displyed when that option is not selected.
- I can't get any pull, backup etc. commands to work.
All of this is probably because I never activated the developer options on my phone. So my question is basically can I retreive my data in any way, or can I somehow activate the developer options with what I have right now.
Another option I got recommended is getting a clean Anroid ROM and loading it with the option "Apply update from SD card" or trying to use "sideload" again to get it there. But I can not find a clean Image of Android for the Motorola G7 power anywhere that I could try out, only custom ROMS and I know that these will delete my data for certain.
I would be very thankfull for any recommendations.
this is what the ADB commands spit out:
(with "Apply Update from ADB" running)
PS C:\adb\platform-tools> .\adb devices
List of devices attached
ZY3266SVDK sideload
(in Fastboot):
PS C:\adb\platform-tools> .\adb devices
List of devices attached
PS C:\adb\platform-tools> .\adb pull "sdcard"
adb: error: failed to get feature set: no devices/emulators found
PS C:\adb\platform-tools> .\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(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: ZY3266SVDK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x2a
(bootloader) uid: D7DCF56600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359507099705734
(bootloader) meid:
(bootloader) date: 06-04-2019
(bootloader) sku: XT1955-2
(bootloader) carrier_sku: XT1955-2
(bootloader) battid: SB18C28957
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 6 17:46:47 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPOS29.114-
(bootloader) ro.build.fingerprint[1]: 134-13/6abfe:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.18.ocean.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_26.100.01.120.03R OCEAN_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld105) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 09:26:39 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-516ad1ccba-200403
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) devcfg.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) keymaster.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) prov.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: protected (277)
(bootloader) ro.carrier: altmx
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.154s
Jhon3323 said:
After updating by itself with almost empty battery (probably to Android 10) my device wont boot up anything except Fastboot and Recovery Mode. On this device I did not modify anything at all previously, no root, no custom bootloader no nothing. I did not even unlock developer options/usb debugging in the settings, which is probably what now haunts me. I know a factory reset will be an easy fix, but I would really like to recover at least some data first, which seems pretty impossible to do but im not just ready to give up.
I can get very limitied acces through ADB.
- If I choose "Apply update from ADB" in Recovery mode, my PC reconizes the device in the device-manager and I can choose drivers etc. But obvioulsly not view files in the explorer or anythng else helpful.
- The command "fastboot getvar all" works and spits out a huge list of variables about the phone
- The command "adb devices" displays a number and "sideload" when the option "Apply update from ADB" is selected in the Recovery, but nothing at all is displyed when that option is not selected.
- I can't get any pull, backup etc. commands to work.
All of this is probably because I never activated the developer options on my phone. So my question is basically can I retreive my data in any way, or can I somehow activate the developer options with what I have right now.
Another option I got recommended is getting a clean Anroid ROM and loading it with the option "Apply update from SD card" or trying to use "sideload" again to get it there. But I can not find a clean Image of Android for the Motorola G7 power anywhere that I could try out, only custom ROMS and I know that these will delete my data for certain.
I would be very thankfull for any recommendations.
this is what the ADB commands spit out:
(with "Apply Update from ADB" running)
PS C:\adb\platform-tools> .\adb devices
List of devices attached
ZY3266SVDK sideload
(in Fastboot):
PS C:\adb\platform-tools> .\adb devices
List of devices attached
PS C:\adb\platform-tools> .\adb pull "sdcard"
adb: error: failed to get feature set: no devices/emulators found
PS C:\adb\platform-tools> .\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(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: ZY3266SVDK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x2a
(bootloader) uid: D7DCF56600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359507099705734
(bootloader) meid:
(bootloader) date: 06-04-2019
(bootloader) sku: XT1955-2
(bootloader) carrier_sku: XT1955-2
(bootloader) battid: SB18C28957
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 6 17:46:47 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPOS29.114-
(bootloader) ro.build.fingerprint[1]: 134-13/6abfe:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.18.ocean.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_26.100.01.120.03R OCEAN_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld105) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 09:26:39 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-516ad1ccba-200403
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) devcfg.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) keymaster.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) prov.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: protected (277)
(bootloader) ro.carrier: altmx
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.154s
Click to expand...
Click to collapse
Have u tried to fastboot a recovery image like orange fox if u still need more help head over to Moto g7 power soport group in tellagram
roadkill42 said:
Have u tried to fastboot a recovery image like orange fox if u still need more help head over to Moto g7 power soport group in tellagram
Click to expand...
Click to collapse
Oh ok thanks a lot I will look into that. Is "mG7Power" the group?
Jhon3323 said:
Oh ok thanks a lot I will look into that. Is "mG7Power" the group?
Click to expand...
Click to collapse
Motog7 power suport force. Or motog7 power suport

Help: Repair reboot after wipe failed

I tried to install the official TWRP/Magisk. Everything seem to be ok (I unlocked it) until I was on the step of "Format Data" on TWRP for deencryption. No commands showed and the loading bar was moving and moving.... I waited 8 hours but nothing seem to be happening. I turned off the phone and now it just reboots in loop. I am still able to access both the Fastboot and TWRP. When I access to TWRP first reboots (I guess it change the slot from A to B, because TWRP seems to be working only with B) then it access normally.
Please help I just want to fix the phone even if I dont root it. I tried to use the Lenovo Rescue tool but just shows the message "Unable to match the appropiate firmware. Some key information cannot be read from device".
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-6a359c146ce-200818
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB SAMSUNG KLUDG4U1EA-B0C1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=01 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: ZY3263GPSQ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x03
(bootloader) uid: 0000010C8F2A98FA0000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1970-2
(bootloader) carrier_sku: XT1970-2
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Sep 21 16:40:40 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/kane_amx/kane_sprout:10/Q
(bootloader) ro.build.fingerprint[1]: SAS30.62-28-8/ea919:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.samsung: 20190525
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2881431
(bootloader) kernel.version[0]: Linux version 4.14.113-user+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (https://and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Tue Aug 18 05:39:54 CDT 2020
(bootloader) bootloader.git: MBM-2.2-kane_retail-6a359c146ce-200818
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxmx
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.597s
As you can see my phone is the T1970-2 from Mexico. I wanted to try some firmware I found when I google it but i dont want to mess it . Thanks in advance.
alankat said:
I tried to install the official TWRP/Magisk. Everything seem to be ok (I unlocked it) until I was on the step of "Format Data" on TWRP for deencryption. No commands showed and the loading bar was moving and moving.... I waited 8 hours but nothing seem to be happening. I turned off the phone and now it just reboots in loop. I am still able to access both the Fastboot and TWRP. When I access to TWRP first reboots (I guess it change the slot from A to B, because TWRP seems to be working only with B) then it access normally.
Please help I just want to fix the phone even if I dont root it. I tried to use the Lenovo Rescue tool but just shows the message "Unable to match the appropiate firmware. Some key information cannot be read from device".
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-6a359c146ce-200818
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB SAMSUNG KLUDG4U1EA-B0C1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=01 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: ZY3263GPSQ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x03
(bootloader) uid: 0000010C8F2A98FA0000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1970-2
(bootloader) carrier_sku: XT1970-2
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Sep 21 16:40:40 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/kane_amx/kane_sprout:10/Q
(bootloader) ro.build.fingerprint[1]: SAS30.62-28-8/ea919:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.samsung: 20190525
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2881431
(bootloader) kernel.version[0]: Linux version 4.14.113-user+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (https://and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Tue Aug 18 05:39:54 CDT 2020
(bootloader) bootloader.git: MBM-2.2-kane_retail-6a359c146ce-200818
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxmx
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.597s
As you can see my phone is the T1970-2 from Mexico. I wanted to try some firmware I found when I google it but i dont want to mess it . Thanks in advance.
Click to expand...
Click to collapse
In my youtube channel Eufracio lopez available a video called Start up Failed Motorola One Vision
hello, Did any one have persist partition for xt1970-5. after flash linageos im lost baseband and imei.
Best regards
Rafal

"Dynamic System Update" package bricked phone

I installed a "Dynamic System Update" package and after rebooting the OS is not detected, bootloader (Vol D + Power) opens, but start and recovery lead to the same missing os screen.
Is there some way to fix this? I need my phone working
I can get to fastboot but not adb, this is `fastboot getvar all`
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-df63f3de4a8-210524
(bootloader) product: denver
(bootloader) board: denver
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM5V8001DM-B622 FV=2702 WB=2048
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_MANNAR 1.1
(bootloader) serialno: ZY22CKXBPJ
(bootloader) cid:
(bootloader) channelid: 0x99
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 788201472
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 06-16-2021
(bootloader) sku: XT2131-1
(bootloader) carrier_sku: XT2131-1
(bootloader) battid: SB18D00294
(bootloader) battery-voltage: 4333
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: boost
(bootloader) ro.build.fingerprint[0]: motorola/denver_global/denver:11/R
(bootloader) ro.build.fingerprint[1]: RE31.Q2-11-52/a40ec:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.9.16.r1-03500-MANNAR.0
(bootloader) version-baseband[0]: M4350_HI405_19.533.01.79R DENVER_BOOST
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 5.4.61-moto-gfa1749a591f9
(bootloader) kernel.version[1]: ([email protected]) (Android (6443078
(bootloader) kernel.version[2]: based on r383902) clang version 11.0.1
(bootloader) kernel.version[3]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[4]: ain/llvm-project b397f81060ce6d701042b78
(bootloader) kernel.version[5]: 2172ed13bee898b79), LLD 11.0.1 (/buildbo
(bootloader) kernel.version[6]: t/tmp/tmp6_m7QH b397f81060ce6d701042b782
(bootloader) kernel.version[7]: 172ed13bee898b79)) #1 SMP PREEMPT Mon Ma
(bootloader) kernel.version[8]: y 24 04:24:01 CDT 2021
(bootloader) git:xbl: MBM-3.0-uefi-71c7a1ab-210524
(bootloader) git:xbl_config: MBM-3.0-uefi-71c7a1ab-210524
(bootloader) git:abl: MBM-3.0-uefi-df63f3de4a8-210524
(bootloader) git:rpm: MBM-3.0-uefi-1573f88-210524
(bootloader) git:tz: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:hyp: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:devcfg: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:keymaster: MBM-3.0-uefi-9731016-210524
(bootloader) git:storsec: MBM-3.0-uefi-9731016-210524
(bootloader) git:uefisecapp: MBM-3.0-uefi-9731016-210524
(bootloader) gitrov: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:qupfw: MBM-3.0-uefi-7b29c10-210524
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(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: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C93368
(bootloader) primary-display: auo_nt36675_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.159s
Click to expand...
Click to collapse
ShayBox said:
I installed a "Dynamic System Update" package and after rebooting the OS is not detected, bootloader (Vol D + Power) opens, but start and recovery lead to the same missing os screen.
Is there some way to fix this? I need my phone working
I can get to fastboot but not adb, this is `fastboot getvar all`
Click to expand...
Click to collapse
The bootloader is locked, I doubt it can be fixed.
A slightly bigger doubt. How is the device detected as a PVT??
You can also just go to recovery and send us an image to show what it says , maybe the Lenovo Motorola Smart Assistant will help (QFIL flash tool with a good looking UI for Lenovo and moto devices , destroyed my tab due to the Lenovo Smart Assistant installing the firmware in a wrong method causing failures! but lets hope yours will survive!)
Slot b retry count is 0 , we could retry to set slot b as primary slot it might just work! but locked bootloaders don't allow this.... maybe just maybe you can ask Moto about this and they might be able to help , the device is QCOM based so QFIL should work (Lenovo Smart Assistant should also work????)
Seems lenovo moto smart assistant isn't working because support.lenovo.com is down until tomorrow.
Can the device be unlocked like this? or is that a bad idea.
I just got this phone 2 days ago, bought it after breaking my old free phone screen
ShayBox said:
Seems lenovo moto smart assistant isn't working because support.lenovo.com is down until tomorrow.
Can the device be unlocked like this? or is that a bad idea.
I just got this phone 2 days ago, bought it after breaking my old free phone screen
Click to expand...
Click to collapse
I doubt LMSA can help, it pulls info from the phone to match firmware.
Getvar all doesn't show the info needed, so you would just get an error from LMSA.
You should try Moto support
sd_shadow said:
I doubt LMSA can help, it pulls info from the phone to match firmware.
Getvar all doesn't show the info needed, so you would just get an error from LMSA.
You should try Moto support
Click to expand...
Click to collapse
support.motorola.com is also broken, but not for maintenance so who knows how long that will take to work again, this sucks...
EDIT: Its back online, I'll try it
IT WORKED! I used the updated lenovo software and it worked!

Moto G7 Power (unmodified) start up sticks on Moto logo screen

My son has a completely standard Moto G7 Power which has suddenly decided not to boot up. When power button is pressed it displays the Moto M logo screen for a while, vibrates and then powers off. Charging function and display works fine. The phone has not been modded in any way since new - the only change was probably an OTA update from android 9 to 10.
I can get into fastboot and recovery modes on the phone. Searching around it seems from other threads that it should be possible to recover phone by reflashing appropriate stock rom (this is UK version XT1955-4). However I am not having any success. I have tried both Lenovo Rescue LMSA and RSD Lite. Both seem to go through the process OK but when it comes to end and they reboot phone it behaves exactly as before.
One point I am not clear on is whether the phone must be oem unlocked to perform a reflash? I have seen this question asked several times in other threads but could find no answer provided. Some posts suggest that reflashing stock rom should work even with oem lock on provided it is the same (or later version?) as current rom on phone?
The phone is currently oem locked according to fastboot screen. I know how to unlock using developer option and Motorola supplied unlock code etc. but obviously I cannot get into android settings as phone currently does not boot.
The fastboot getvar is below.
F:\AndroidADK>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-cfdb645cf1d-210201
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(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: ZY3274FD52
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: F53196C300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ********************
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-07-2019
(bootloader) sku: XT1955-4
(bootloader) carrier_sku: XT1955-4
(bootloader) battid: SB18C28957
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 10 15: 6:39 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ocean_reteu/ocean:10/QPOS
(bootloader) ro.build.fingerprint[1]: 30.52-29-7-6/7287f:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_43.192.01.165R OCEAN_ROW_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Mon Feb 1 08:18
(bootloader) kernel.version[3]: :38 CST 2021
(bootloader) sbl1.git: MBM-2.1-ocean_retail-315bc626c6-210201
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-210201
(bootloader) tz.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) devcfg.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) keymaster.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) prov.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) aboot.git: MBM-2.1-ocean_retail-cfdb645cf1d-210201
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P7SP
all: listed above
Finished. Total time: 0.114s
Additional info missing from original post which may help:-
Obviously tried factory reset, cache wipe etc.
Bootloader gives following message:-
Start Up Failed .... Use Software Repair Assistant.... etc.
AP Fastboot Flash Mode (Secure)
SSM: Andorid image roll back: 19,20
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
Any suggestions folks?

Failed to get unlock data

I want to put LOS on my new Motorola One 5G Ace (XT2113-2). I downloaded platform tools from here, enabled OEM unlock and USB debugging in settings, and restarted the phone with adb restart bootloader. While in fastboot, fastboot devices showed the device, but every time I tried fastboot oem get_unlock_data it would hang for a while, give up with the following error and reboot into fastboot again:
Code:
% ./fastboot oem get_unlock_data
FAILED (Status read failed (No such device))
fastboot: error: Command failed
I read somewhere that this needs to be done on Windows, so I booted up Windows and downloaded platform tools from here, downloaded the USB driver from here, installed that, rebooted everything and tried again. This time fastboot oem get_unlock_data gave up immediately with another error:
Code:
> fastboot oem get_unlock_data
(bootloader) Failed to get unlock data.
OKAY [ 0.012s]
Finished. Total time: 0.012s
I read somewhere else that I needed to put a SIM card in the device and wait a while. I also tried enabling data before rebooting into fastboot, as well as various USB cables and ports. On two different PCs.
Any ideas?
Code:
% fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-kiev_t-65b8d7a21e0-220703
(bootloader) product: kiev
(bootloader) board: kiev
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM2V8001CM-B707 FV=1500 WB=16777216
(bootloader) ram: 6GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 10
(bootloader) cpu: SM_BITRA_H 1.0
(bootloader) serialno: ***
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 72BAAEEC
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: allowed
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ***
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 01-05-2021
(bootloader) sku: XT2113-2
(bootloader) carrier_sku: XT2113-2
(bootloader) battid: SB18C85232
(bootloader) battery-voltage: 4027
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: unknown
(bootloader) ro.build.fingerprint[0]: motorola/kiev_t/kiev:11/RZKS31.Q3-
(bootloader) ro.build.fingerprint[1]: 45-16-3-3/d1c34:user/release-keys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-12500-SMxx50.0
(bootloader) version-baseband: M7225_HI251_22.578.01.39R KIEV_TMO_CUST
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Sun J
(bootloader) kernel.version[4]: ul 3 10:35:18 CDT 2022
(bootloader) git:xbl: MBM-3.0-kiev_t-93822280-220703
(bootloader) git:xbl_config: MBM-3.0-kiev_t-93822280-220703
(bootloader) git:abl: MBM-3.0-kiev_t-65b8d7a21e0-220703
(bootloader) git:aop: MBM-3.0-kiev_t-f135681-220703
(bootloader) git:tz: MBM-3.0-kiev_t-5761219a-220703
(bootloader) git:hyp: MBM-3.0-kiev_t-5761219a-220703
(bootloader) git:devcfg: MBM-3.0-kiev_t-5761219a-220703
(bootloader) git:keymaster: MBM-3.0-kiev_t-775ecfe-220703
(bootloader) git:storsec: MBM-3.0-kiev_t-775ecfe-220703
(bootloader) git:uefisecapp: MBM-3.0-kiev_t-775ecfe-220703
(bootloader) git:prov: MBM-3.0-kiev_t-5761219a-220703
(bootloader) git:qupfw: MBM-3.0-kiev_t-0ae1dc5-220703
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C93430
(bootloader) primary-display: csot_ft8756_666_1080x2400_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.050s

Categories

Resources