Please help, am I bricked? How do I get out of this?? - Moto G7 Power Questions & Answers

I have the XT1955-5 , I recently tried rooting it and it won't boot up at all. TWRP and fastboot will load but it always loops "your device has been unlocked and cannot be trusted" "ID: n/a" whenever I try and start it into anything. Please help? I'm really worried I may have bricked this and cannot afford another one at this time.

How hard to flash the stock firmware when you are in the fastboot mode ?
If you still cannot do it, pay someone to do it for you.
Sent from my LG-LS997 using Tapatalk

blumyu said:
I have the XT1955-5 , I recently tried rooting it and it won't boot up at all. TWRP and fastboot will load but it always loops "your device has been unlocked and cannot be trusted" "ID: n/a" whenever I try and start it into anything. Please help? I'm really worried I may have bricked this and cannot afford another one at this time.
Click to expand...
Click to collapse
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

cgigate said:
How hard to flash the stock firmware when you are in the fastboot mode ?
If you still cannot do it, pay someone to do it for you.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
I tried flashing it manually last night using fastboot to flash the files one by one but it didn't seem to work...
---
sd_shadow said:
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
I try to connect it with USB and it gives me this error. I have the drivers installed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

blumyu said:
I tried flashing it manually last night using fastboot to flash the files one by one but it didn't seem to work...
---
I try to connect it with USB and it gives me this error. I have the drivers installed
Click to expand...
Click to collapse
Then , you cannot make it work, pay someone to flash for you.
What does it look like on your fastboot mode ?
Sent from my LG-LS997 using Tapatalk

cgigate said:
Then , you cannot make it work, pay someone to flash for you.
What does it look like on your fastboot mode ?
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
For anything seemingly out of the ordinary:
AP Fastboot Flash Mode (Secure)
BL: MBM-2.1-ocean_t-f71f50d-200210
Baseband: (not found)
Product/Variant: ocean XT1955-5 32GB PVT1
Serial Number: (number here)
Console [NULL]: null
flashing_unlocked

blumyu said:
For anything seemingly out of the ordinary:
AP Fastboot Flash Mode (Secure)
BL: MBM-2.1-ocean_t-f71f50d-200210
Baseband: (not found)
Product/Variant: ocean XT1955-5 32GB PVT1
Serial Number: (number here)
Console [NULL]: null
flashing_unlocked
Click to expand...
Click to collapse
You baseband is gone.
You flashed wrong version firmware without backup.
Sent from my LG-LS997 using Tapatalk

cgigate said:
You baseband is gone.
You flashed wrong version firmware without backup.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Is there anything I can do about this?

blumyu said:
Is there anything I can do about this?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138

blumyu said:
Is there anything I can do about this?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
To see where the getvar all shows
Model#, codename, software channel, and software version
Sent from my ali using XDA Labs

@blumyu Always a good idea to read everything there is for your device and understand it before you begin modding it. And when I say this I'm speaking to myself as well. I've been flashing roms since the Nexus S days and that's been a while but starting with this device I made a new rule for myself and that's I will read the entire forum first and understand it before I begin modding from now on. This device taught me to do that because I had some hard bricks early on and it could have been prevented had I read and understood what I was doing. Thank God for ./Blankflash.sh or I would not have this device anymore. You can learn just about anything you want and pretty quickly nowadays because of the internet. Most things that have to do with Android are already on here on xda some place it's just a matter of searching for them. Sometimes the act of a simple thing like "searching" can take a while. Alot of the time it does for me. Sometimes my answer is hidden in another xda thread or for the same device but maybe a different model #.. I bet the average person who searches for something online doesn't have nothing on one of us who's been addicted to Android for some years. Haha. Cheers.

I need help people, I bought my mom a 1955-2 from Amazon in February, everything was ok until the last security update, the phone rebooted and then went to a state in which it will show the boot screen and then shut down, I'm able to get into FastBoot mode and while checking I saw the same issue, the baseband is gone.
(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 SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326RPM4M
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: D8BABCBE00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 10-17-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: "Fri Apr 3 14: 5:44 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(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 (77)
(bootloader) ro.carrier: retla
(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: 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: 4

jarturoar said:
I need help people, I bought my mom a 1955-2 from Amazon in February, everything was ok until the last security update, the phone rebooted and then went to a state in which it will show the boot screen and then shut down, I'm able to get into FastBoot mode and while checking I saw the same issue, the baseband is gone.
(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 SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326RPM4M
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: D8BABCBE00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 10-17-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: "Fri Apr 3 14: 5:44 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(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 (77)
(bootloader) ro.carrier: retla
(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: 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: 4
Click to expand...
Click to collapse
Use fastboot to flash the stock rom
Sent from my moto g(7) supra using Tapatalk

jarturoar said:
I need help people, I bought my mom a 1955-2 from Amazon in February, everything was ok until the last security update, the phone rebooted and then went to a state in which it will show the boot screen and then shut down, I'm able to get into FastBoot mode and while checking I saw the same issue, the baseband is gone.
(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 SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326RPM4M
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: D8BABCBE00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 10-17-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: "Fri Apr 3 14: 5:44 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(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 (77)
(bootloader) ro.carrier: retla
(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: 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: 4
Click to expand...
Click to collapse
Try LMSA Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs

Related

SIM not working after latest update

So, I connected my phone and Lenovo Moto Smart Assistant said that there was an update for my mobile, great, click download and flash after doing backups. After flashing, everything looked fine, except for one thing: it doesn't recognize the SIM card. It's not the SIM card itself, I have already tried with another one and it didn't work, while mine did in another phone. So, what should I do? The only thing I can think of is flashing back to the previous version, but when I did it bootloader.img, boot.img and dtbo.img failed, bootloader saying that it was a previous version.
Niemand385 said:
So, I connected my phone and Lenovo Moto Smart Assistant said that there was an update for my mobile, great, click download and flash after doing backups. After flashing, everything looked fine, except for one thing: it doesn't recognize the SIM card. It's not the SIM card itself, I have already tried with another one and it didn't work, while mine did in another phone. So, what should I do? The only thing I can think of is flashing back to the previous version, but when I did it bootloader.img, boot.img and dtbo.img failed, bootloader saying that it was a previous version.
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
sd_shadow said:
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff2029-200210
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY32689JZN
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 9F416CFA00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 06-14-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Feb 11 6:23: 8 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPOS29.114-
(bootloader) ro.build.fingerprint[1]: 134-10/21fefe:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.12.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: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld165) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Mon Fe
(bootloader) kernel.version[3]: b 10 12:45:16 CST 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-516ad1c-200210
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab3-200210
(bootloader) tz.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) devcfg.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) keymaster.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) prov.git: MBM-2.1-ocean_retail-d9613e6-dirty-200210
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff2029-200210
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: retus
(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: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
Niemand385 said:
run
Click to expand...
Click to collapse
Try to unlock the bootloader
It's the only way you can downgrade Moto firmware
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Setting up and Using adb.exe and fastboot.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
Sent from my ali using XDA Labs
sd_shadow said:
Try to unlock the bootloader
It's the only way you can downgrade Moto firmware
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Setting up and Using adb.exe and fastboot.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Sooo, this time it worked, thanks for the help.
I was ready to throw the towel, admit that I probably ****ed it up taking the SD card out or something and try my hand at a little hardware fix, but decided to keep up with it because, like, what's the worst that can happen when you flash something and it says that the command failed, right? A little brick never hurt anybody. So I did it, and now it recognizes the SIM again, which is great.

OTA Update after RSA broke my moto g7 power x1955-2?

I'm at a loss. My phone stopped booting when an OTA update was applied and then my phone battery died. I downloaded Rescue and Smart Assistant, and it immediately recognized my phone and proceeded to repair the phone. It booted just fine and I then used it all day. Again an OTA update came in, and I accepted it. I continued using my phone throughout the day, but when I went to reboot, was presented with the following error:
Code:
SSM: Android image roll back: 12, 13
failed to validate boot image
failed to pass validation, backup to fastboot
I figured I'd go back to the Rescue and Smart Assistant, but it is now telling me I have an unsupported device, whether I try to automatically detect the phone or enter the X1955-2.
My bootloader is not unlocked, I haven't rooted the phone and is otherwise all stock from Amazon. What can I do from here? I cannot afford a new phone and my life is hard without access to one.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0a6142d67e0-200508
(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: ZY323TZHD9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: CC606A9F00000000000000000000
(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: 04-11-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: "Fri Jun 26 7:31:58 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QPOS30.52-
(bootloader) ro.build.fingerprint[1]: 29-2/397fb:user/release-keys
(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_41.178.01.156R OCEAN_LATAMDSDS_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 Sun May 24 10:3
(bootloader) kernel.version[3]: 3:41 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-315bc626c6-200508
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-200508
(bootloader) tz.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) devcfg.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) keymaster.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) prov.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) aboot.git: MBM-2.1-ocean_retail-0a6142d67e0-200508
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retla
(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
(bootloader) pcb-part-no: SP69A6P0ME
all: listed above
finished. total time: 0.021s
nickrfroberts said:
I'm at a loss. My phone stopped booting when an OTA update was applied and then my phone battery died. I downloaded Rescue and Smart Assistant, and it immediately recognized my phone and proceeded to repair the phone. It booted just fine and I then used it all day. Again an OTA update came in, and I accepted it. I continued using my phone throughout the day, but when I went to reboot, was presented with the following error:
Code:
SSM: Android image roll back: 12, 13
failed to validate boot image
failed to pass validation, backup to fastboot
I figured I'd go back to the Rescue and Smart Assistant, but it is now telling me I have an unsupported device, whether I try to automatically detect the phone or enter the X1955-2.
My bootloader is not unlocked, I haven't rooted the phone and is otherwise all stock from Amazon. What can I do from here? I cannot afford a new phone and my life is hard without access to one.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0a6142d67e0-200508
(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: ZY323TZHD9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: CC606A9F00000000000000000000
(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: 04-11-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: "Fri Jun 26 7:31:58 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QPOS30.52-
(bootloader) ro.build.fingerprint[1]: 29-2/397fb:user/release-keys
(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_41.178.01.156R OCEAN_LATAMDSDS_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 Sun May 24 10:3
(bootloader) kernel.version[3]: 3:41 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-315bc626c6-200508
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-200508
(bootloader) tz.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) devcfg.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) keymaster.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) prov.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) aboot.git: MBM-2.1-ocean_retail-0a6142d67e0-200508
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retla
(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
(bootloader) pcb-part-no: SP69A6P0ME
all: listed above
finished. total time: 0.021s
Click to expand...
Click to collapse
Could try RSD Lite if you have a pc running something lower than 10 like windows 7.
What is the firmware name rsa used?
It will be in something like c/program data/lmsa/downloads/romfiles
Sent from my Moto E (4) using Tapatalk

[Solved: warranty repair] No bootable and OEM locked

Solved: warranty repair
Sorry for the delay (I picked up the phone today)
So, the warranty accepted the repair :victory:
Anyway, thank you very much guys :laugh:
Hi guys!
I researched all day about it and I tried all the tutorials I found, nothing
I read that it is only possible with "BOX" like "Medusa Pro", is there another way to fix this?
I hope so, don't have money for it now :crying:
Thank you anyway
fastboot getvar all:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-0820bb9-191106
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno:
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 171FCC60
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805257216
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-19-2019
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid:
(bootloader) battery-voltage: 4092
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:9/PPIS29.65-51-
(bootloader) ro.build.fingerprint[1]: 5/ae5dc:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.4.doha.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.11.r1-03300-NICOBAR.0
(bootloader) version-baseband: M6125_06.09.02.10R DOHA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.98-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld120) (clang version 6.0.9 for Andro
(bootloader) kernel.version[2]: id NDK) #1 SMP PREEMPT Sun May 24 12:39:
(bootloader) kernel.version[3]: 16 CDT 2020
(bootloader) git:abl: MBM-3.0-doha_retail-0820bb9-191106
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(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: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) pcb-part-no:
Photos the screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try flashing blankflash
Deathgasm said:
try flashing blankflash
Click to expand...
Click to collapse
Good luck booting to EDL mode with locked bootloader.
Sent from my ali using XDA Labs
Use the Lenovo moto smart assistant to flash your device and fix your problem.
JeanLucas00 said:
Hi guys!
I researched all day about it and I tried all the tutorials I found, nothing
I read that it is only possible with "BOX" like "Medusa Pro", is there another way to fix this?
I hope so, don't have money for it now :crying:
Thank you anyway
fastboot getvar all:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-0820bb9-191106
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno:
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 171FCC60
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805257216
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-19-2019
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid:
(bootloader) battery-voltage: 4092
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:9/PPIS29.65-51-
(bootloader) ro.build.fingerprint[1]: 5/ae5dc:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.4.doha.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.11.r1-03300-NICOBAR.0
(bootloader) version-baseband: M6125_06.09.02.10R DOHA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.98-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld120) (clang version 6.0.9 for Andro
(bootloader) kernel.version[2]: id NDK) #1 SMP PREEMPT Sun May 24 12:39:
(bootloader) kernel.version[3]: 16 CDT 2020
(bootloader) git:abl: MBM-3.0-doha_retail-0820bb9-191106
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(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: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) pcb-part-no:
Photos the screen:
Click to expand...
Click to collapse
Did you take a look at this post? https://forum.xda-developers.com/moto-g8-plus/help/hardbicked-g8-plus-t4108065
I had the same problem I think and finally can fix it
Solved: warranty repair
Sorry for the delay (I picked up the phone today)
So, the warranty accepted the repair :victory:
Anyway, thank you very much guys :laugh:

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

Help me find my Stock Rom, Flashing Locked, No System

I brick my moto g8 plus and i cannot find the correct firmware to flash it, and i have bootloader locked, i was trying to install a GSI ROM and everything was ok, until i lock the bootloader and realize what have i done
I tried everything already, this is my only hope
The things i tried include:
QFIL(the programmer file for this is inside the blankflash, and the rawprogram0 and patch0 i generate from gpt.bin), and when its gonna flash something after the files of the bootloader it say the error "range restricted", and i cannot flash anything after that, i cannot either read partitions that are not the bootloader, i was looking for modified the programmer or something else but didn't work
I tried modified the blankflash commands that is inside of singleimage.bin. When i tried to "<oem value="unlock"/> it says that "handler oem not allowed", and the same happens with "<flashing value="unlock"/>" then "handler flashing not allowed"
i tried already LMSA and get error at 50%
if anyone wants more information for what i did with QFIL tell me
Sorry for my bad english
here's my getvar
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-7326ad2e6a-210530
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY227DLRRR
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 82125579
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805263360
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: XXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-27-2020
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid: SB18C52858
(bootloader) battery-voltage: 3605
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: attmx
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPIS30.28-Q3
(bootloader) ro.build.fingerprint[1]: -28-26-4-1-4/c46067:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.45R DOHA_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Sun May 30 11:
(bootloader) kernel.version[3]: 12:12 CDT 2021
(bootloader) git:xbl: MBM-3.0-doha_retail-bdc252f49-210530
(bootloader) git:xbl_config: MBM-3.0-doha_retail-bdc252f49-210530
(bootloader) git:rpm: MBM-3.0-doha_retail-cea405b-210530
(bootloader) git:tz: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:hyp: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:devcfg: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:cmnlib: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:cmnlib64: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:keymaster: MBM-3.0-doha_retail-30e77003-210530
(bootloader) gitrov: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:abl: MBM-3.0-doha_retail-7326ad2e6a-210530
(bootloader) git:qupfw: MBM-3.0-doha_retail-25b246c-210530
(bootloader) git:uefisecapp: MBM-3.0-doha_retail-30e77003-210530
(bootloader) frp-state: no protection (0)
(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
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C71289
all: listed above
CarlyArcadia said:
I brick my moto g8 plus and i cannot find the correct firmware to flash it, and i have bootloader locked, i was trying to install a GSI ROM and everything was ok, until i lock the bootloader and realize what have i done
I tried everything already, this is my only hope
The things i tried include:
QFIL(the programmer file for this is inside the blankflash, and the rawprogram0 and patch0 i generate from gpt.bin), and when its gonna flash something after the files of the bootloader it say the error "range restricted", and i cannot flash anything after that, i cannot either read partitions that are not the bootloader, i was looking for modified the programmer or something else but didn't work
I tried modified the blankflash commands that is inside of singleimage.bin. When i tried to "<oem value="unlock"/> it says that "handler oem not allowed", and the same happens with "<flashing value="unlock"/>" then "handler flashing not allowed"
i tried already LMSA and get error at 50%
if anyone wants more information for what i did with QFIL tell me
Sorry for my bad english
here's my getvar
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-7326ad2e6a-210530
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY227DLRRR
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 82125579
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805263360
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: XXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-27-2020
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid: SB18C52858
(bootloader) battery-voltage: 3605
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: attmx
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPIS30.28-Q3
(bootloader) ro.build.fingerprint[1]: -28-26-4-1-4/c46067:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.45R DOHA_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Sun May 30 11:
(bootloader) kernel.version[3]: 12:12 CDT 2021
(bootloader) git:xbl: MBM-3.0-doha_retail-bdc252f49-210530
(bootloader) git:xbl_config: MBM-3.0-doha_retail-bdc252f49-210530
(bootloader) git:rpm: MBM-3.0-doha_retail-cea405b-210530
(bootloader) git:tz: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:hyp: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:devcfg: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:cmnlib: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:cmnlib64: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:keymaster: MBM-3.0-doha_retail-30e77003-210530
(bootloader) gitrov: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:abl: MBM-3.0-doha_retail-7326ad2e6a-210530
(bootloader) git:qupfw: MBM-3.0-doha_retail-25b246c-210530
(bootloader) git:uefisecapp: MBM-3.0-doha_retail-30e77003-210530
(bootloader) frp-state: no protection (0)
(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
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C71289
all: listed above
Click to expand...
Click to collapse
This is
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have one more updated version https://mirrors.lolinet.com/firmware/moto/doha/official/ATTMX/ See the date 2021-08-24 but you could try first with the same.
Here are also the blank files available https://mirrors.lolinet.com/firmware/moto/doha/blankflash/
SubwayChamp said:
This is
View attachment 5424239
You have one more updated version https://mirrors.lolinet.com/firmware/moto/doha/official/ATTMX/ See the date 2021-08-24 but you could try first with the same.
Here are also the blank files available https://mirrors.lolinet.com/firmware/moto/doha/blankflash/
Click to expand...
Click to collapse
I already have that version and said that i don't have permissions to flash :c, i tried with that and with the retail but it doesn't work
CarlyArcadia said:
I already have that version and said that i don't have permissions to flash :c, i tried with that and with the retail but it doesn't work
Click to expand...
Click to collapse
Well, you said you need to find the proper firmware for your device and this is the proper one.
The error you are getting from the tool may come from other reason, I used qfil sometimes to unbrick a pair of devices and never had any issues, you have to put your device in EDL mode, the fire programmer file has to be the proper too.
Fastboot is not available for you due to your mistake to re-lock bootloader while you are using something custom onto your device.
SubwayChamp said:
Well, you said you need to find the proper firmware for your device and this is the proper one.
The error you are getting from the tool may come from other reason, I used qfil sometimes to unbrick a pair of devices and never had any issues, you have to put your device in EDL mode, the fire programmer file has to be the proper too.
Fastboot is not available for you due to your mistake to re-lock bootloader while you are using something custom onto your device.
Click to expand...
Click to collapse
I think that i was in the incorrect firmware, i already use the proper programmer file, it wont let flash anything after the sector 77824.
Maybe the programmer file that i get from the blankflash only let to flash to the sector 77824, that sector are from the bootloader
That is the only programmer that i found for SDM665 EMMC :c
CarlyArcadia said:
I think that i was in the incorrect firmware, i already use the proper programmer file, it wont let flash anything after the sector 77824.
Maybe the programmer file that i get from the blankflash only let to flash to the sector 77824, that sector are from the bootloader
That is the only programmer that i found for SDM665 EMMC :c
Click to expand...
Click to collapse
You'd need to read every possible workaround to overcome this, unfortunately there is not a simple receipt, here one of the guides you can see
SubwayChamp said:
You'd need to read every possible workaround to overcome this, unfortunately there is not a simple receipt, here one of the guides you can see
Click to expand...
Click to collapse
Thank you for your help. but already did the same as the guy in the video, and for him at least it work because it have the bootloader unlock, i going to keep trying to modified the programmer file to let flash everything
CarlyArcadia said:
Thank you for your help. but already did the same as the guy in the video, and for him at least it work because it have the bootloader unlock, i going to keep trying to modified the programmer file to let flash everything
Click to expand...
Click to collapse
Any update? I have a phone that has the same problem as yours, except i can use the blankflash and it works.
Could you share your QFIL files by the way?
setryky said:
Any update? I have a phone that has the same problem as yours, except i can use the blankflash and it works.
Could you share your QFIL files by the way?
Click to expand...
Click to collapse
It work's for me too, but its still locked the bootloader
If you have any news, let me know, I also have a similar problem
CarlyArcadia said:
I brick my moto g8 plus and i cannot find the correct firmware to flash it, and i have bootloader locked, i was trying to install a GSI ROM and everything was ok, until i lock the bootloader and realize what have i done
I tried everything already, this is my only hope
The things i tried include:
QFIL(the programmer file for this is inside the blankflash, and the rawprogram0 and patch0 i generate from gpt.bin), and when its gonna flash something after the files of the bootloader it say the error "range restricted", and i cannot flash anything after that, i cannot either read partitions that are not the bootloader, i was looking for modified the programmer or something else but didn't work
I tried modified the blankflash commands that is inside of singleimage.bin. When i tried to "<oem value="unlock"/> it says that "handler oem not allowed", and the same happens with "<flashing value="unlock"/>" then "handler flashing not allowed"
i tried already LMSA and get error at 50%
if anyone wants more information for what i did with QFIL tell me
Sorry for my bad english
here's my getvar
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-7326ad2e6a-210530
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY227DLRRR
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 82125579
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805263360
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: XXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-27-2020
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid: SB18C52858
(bootloader) battery-voltage: 3605
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: attmx
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPIS30.28-Q3
(bootloader) ro.build.fingerprint[1]: -28-26-4-1-4/c46067:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.45R DOHA_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Sun May 30 11:
(bootloader) kernel.version[3]: 12:12 CDT 2021
(bootloader) git:xbl: MBM-3.0-doha_retail-bdc252f49-210530
(bootloader) git:xbl_config: MBM-3.0-doha_retail-bdc252f49-210530
(bootloader) git:rpm: MBM-3.0-doha_retail-cea405b-210530
(bootloader) git:tz: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:hyp: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:devcfg: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:cmnlib: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:cmnlib64: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:keymaster: MBM-3.0-doha_retail-30e77003-210530
(bootloader) gitrov: MBM-3.0-doha_retail-30e77003-210530
(bootloader) git:abl: MBM-3.0-doha_retail-7326ad2e6a-210530
(bootloader) git:qupfw: MBM-3.0-doha_retail-25b246c-210530
(bootloader) git:uefisecapp: MBM-3.0-doha_retail-30e77003-210530
(bootloader) frp-state: no protection (0)
(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
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C71289
all: listed above
Click to expand...
Click to collapse
Managed to solve?
tirkius said:
If you have any news, let me know, I also have a similar problem
Click to expand...
Click to collapse
Managed to solve?

Categories

Resources