Database Develop

The device is Corrupted, Cannot Be trusted, Will not boot

Hey Guys!
I have a problem with a motorola xt1900 (x4) is stuck in the unlock bootloader notify, I tried many forms by fastboot but did not succeed.
First of all, I installed the lineage 16.0, it was great, but then I wanted to do root, I downloaded the magisk and it gave bootloop after flash, so I tried to put the 8.0 stockrom and I've been stuck ever since, can't unlock again, i still have the code from motorola.
"the device is Corrupted, Can not Be trusted, Will not boot"
I tried to flash the TWRP, but I could not.

I ended up in a semi-hard bricked phone where recovery wouldn't boot and my phone told me both slot A and B was missing. My way of fixing my phone when all I could do was seeing a bootloader with an error message (as you seem to have) was to flash it with the flash all software found here https://www.androidfilehost.com/?fid=890278863836292604 Run flash_all.bat as an administrator in Windows or ./flash_all in Linux as root ( sudo ./flash_all ). Remember, you don't need to enter recovery, the boot error message should be good enough.
The thing you need to accept is all your data will be wiped. If you wanted to save anything, it was already too late. Once you run that flash, reboot your phone into your bootloader and run the command
fastboot boot '/your_path_here/twrp-3.2.3-1-payton.img'
This will force your phone to boot using TWRP from your computer and from there you should be able to upload a ROM and install. -- Remember if using Linux to add the sudo command before that.

Hey man! I'm on Windows.
By the way, don't care about data. just want my phone working.:crying:
still same error message, (bootloader) "flash permission denied"
"remote failure"
I try again the unlock code, says ok finished, but didn't work.

danielwah said:
Hey man! I'm on Windows.
By the way, don't care about data. just want my phone working.:crying:
still same error message, (bootloader) "flash permission denied"
"remote failure"
I try again the unlock code, says ok finished, but didn't work.
Click to expand...
Click to collapse
The same happened to me using the regular adb flashboot commands...I have my X4 totaly locked... Any new?

tuliusy2k said:
The same happened to me using the regular adb flashboot commands...I have my X4 totaly locked... Any new?
Click to expand...
Click to collapse
My errors:
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.

This is my fastboot getvar all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180328
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0039062204
(bootloader) cid: 0x0032
(bootloader) channelid: 0x01
(bootloader) uid: 9EB17BE5
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***********************
(bootloader) meid:
(bootloader) date: 10-10-2017
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3942
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-25/32:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.32.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g18bb7f8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Oct 18 11:48:40 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180328
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180328
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-180328
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180328
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(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
all: listed above
finished. total time: 0.219s
I have the same problem "The device is Corrupted, Cannot Be trusted, Will not boot"

Use the fastboot getvar all command, find the sku version of it and download the rom with the same number that appears in the fastboot and install normally, it worked with me now at dawn. The only rom that works when the unit is in this state and the one in it

i am the same problem...
After relock bootloader it wont boot, dont enter recovery, only enter in fastboot, but flashing is locked!
Any stock system not flash....
---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------
i am the same problem...
After relock bootloader it wont boot, dont enter recovery, only enter in fastboot, but flashing is locked!
Any stock system not flash....

I found the solution! (for me)
1 - Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in my phone. (Lineage 16.0)
https://drive.google.com/file/d/1OaWtQo1jfX5glVj1pnjDnu8NDkgDOHDd/view?usp=sharing
"fastboot boot boot.img"
And the phone enter a System!
2 - Activate ADB, and allow superuser comands in ADB - "Developer Settings"
And run the command for show "Enable OEM Unlocking"
adb shell setprop ro.oem_unlock_supported 1
Check toggle "Enable OEM Unlocking"
3 - Power off and put in fastboot again
4 - re-run "fastboot oem unlock <<your code>>"
5 - Ready! Your phone unlocked flashing again!

I woke up in the morning and found my phone had crashed. I turned it off and it woudlnt come back on. same error message...
your devise is corrupt. it cant be trusted and will not boot.
Has anyone found a way to recover it without losign nay data. i really cant afford to lose my pics and videos.
Any help would be appreciated.
PS i rooted this phone a long time ago and not fluent in the root process

juniofdm said:
I found the solution! (for me)
1 - Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in my phone. (Lineage 16.0)
https://drive.google.com/file/d/1OaWtQo1jfX5glVj1pnjDnu8NDkgDOHDd/view?usp=sharing
"fastboot boot boot.img"
And the phone enter a System!
Click to expand...
Click to collapse
I tried this on my device (never rooted, never unlocked bootloader), and at first it gave me the error:
Sending 'boot.img' (22249 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Then subsequent attempts just get stuck on the 'Sending' line. This was using the stock image from this post: https://forum.xda-developers.com/t/rom-stock-pie-9-0-moto-x4-retail-android-pie.3876156/
I've run out of options as the Rescue and Smart Assistant isn't working either. Any help appreciated.

it worked for me thanks

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

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

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

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

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

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

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

Dear Members,
My friend Have Moto X4 (Out of Warranty) this phone popup always says "Close App". So he cannot use the phone.
We tried to repair the phone 2-3 shops. No one able to solve the issue.
I am new to Android, So I thought to watch some youtube videos and downgrade the OS.
So I tried to reduce the Android version to "PAYTON_RETAIL_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
My bad, I watched only some Youtube videos (munchy) and started the procedure from that video.
After those steps My phone Locked. I tried to get help from him but he says the following.
"your bootloader is locked ..nothing i can do to help". sorry.
I have product vairiant : payton XT1900-2 64GB P4.
Power ok, then "oem_locked".
I am using Windows 10.
Some more information
--------
C:\adb>fastboot devices
ZY224GVR4R fastboot
--------
Fastboot recognize the device. adb not working. I have the Unlock Code from Motorola. But I cannot use it.
C:\adb>fastboot oem unlock WDEJJDCG2WPXNSWBGRT7
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
mobile network not detected.
Tried with Wi-fi, the device search progress bar keeps on running. Didn't find the Hotspots/Wifi Router. There is no next button to proceed.
please advise me the next step. Thanks for the reply and your help.
I have the logs while the first attempt fails and erase everything.
Please help to use the phone. Thanks

patrickjjs said:
Dear Members,
My friend Have Moto X4 (Out of Warranty) this phone popup always says "Close App". So he cannot use the phone.
We tried to repair the phone 2-3 shops. No one able to solve the issue.
I am new to Android, So I thought to watch some youtube videos and downgrade the OS.
So I tried to reduce the Android version to "PAYTON_RETAIL_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
My bad, I watched only some Youtube videos (munchy) and started the procedure from that video.
After those steps My phone Locked. I tried to get help from him but he says the following.
"your bootloader is locked ..nothing i can do to help". sorry.
I have product vairiant : payton XT1900-2 64GB P4.
Power ok, then "oem_locked".
I am using Windows 10.
Some more information
--------
C:\adb>fastboot devices
ZY224GVR4R fastboot
--------
Fastboot recognize the device. adb not working. I have the Unlock Code from Motorola. But I cannot use it.
C:\adb>fastboot oem unlock WDEJJDCG2WPXNSWBGRT7
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
mobile network not detected.
Tried with Wi-fi, the device search progress bar keeps on running. Didn't find the Hotspots/Wifi Router. There is no next button to proceed.
please advise me the next step. Thanks for the reply and your help.
I have the logs while the first attempt fails and erase everything.
Please help to use the phone. Thanks
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
Please post it here, and remove IMEI line
Sent from my Moto E (4) using Tapatalk

Thanks Shadow
sd_shadow said:
Run
Code:
fastboot getvar all
Please post it here, and remove IMEI line
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (0)
(bootloader) serialno: ZY224GVR4R
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: A1A80AC4
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: ---------------
(bootloader) meid:
(bootloader) date: 12-16-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4270
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190409
(bootloader) git:tz: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:hyp: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:devcfg: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:keymaster: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) gitrov: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:storsec: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retin
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.176s
C:\adb>

patrickjjs said:
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (0)
(bootloader) serialno: ZY224GVR4R
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: A1A80AC4
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: ---------------
(bootloader) meid:
(bootloader) date: 12-16-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4270
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190409
(bootloader) git:tz: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:hyp: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:devcfg: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:keymaster: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) gitrov: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:storsec: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retin
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.176s
C:\adb>
Click to expand...
Click to collapse
You cannot unlocked the bootloader unless
Oem unlock is allowed in dev options
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

Help through remote screen
sd_shadow said:
You cannot unlocked the bootloader unless
Oem unlock is allowed in dev options
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi Shadow, Can you help through Team viewer or Anydesk, if possible.
Thanks

Process device information screen
patrickjjs said:
Hi Shadow, Can you help through Team viewer or Anydesk, if possible.
Thanks
Click to expand...
Click to collapse
Hi Shadow,
It pops up "Process device information screen " for more than 10 mins. It never returned anything.
Progress bar going on and going on.....
Tested with two times with Admin mode.
Any ideas.
Thanks

hello, could you solve your problem, for my adb if it works, that's why it returns the serial number in the command window, I think you are only trying to flash the wrong firmware, since it is not necessary to have the bootloader unlocked to flash via adb, you have to download a firmware xt1900-2 retail, regards

Solved?
patrickjjs said:
Hi Shadow,
It pops up "Process device information screen " for more than 10 mins. It never returned anything.
Progress bar going on and going on.....
Tested with two times with Admin mode.
Any ideas.
Thanks
Click to expand...
Click to collapse
Did you ever got it working? i'm probably on the same Scenario, tried a lot of stuff, but no sucess.

Another corrupted X4, am I screwed?

My Wife has an X4, xt1900-1 from Google Fi, that she no longer uses as a phone but uses it on wifi only to run a special piece of software. It got the "device is corrupted" error and will not boot to anything other than FastBoot. Adding results of "Fastboot getvar all" at the end of post. Running "Fastboot oem get_unlock_data" returns:
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
Finished. Total time: 0.003s
Running LMSA initially wouldn't detect the device, then it did detect and begins the re-flash process but fails at flashing around 69 percent.(nice) No other information is given other than flashing failed.
Attempting to flash the firmware that the LMSA downloaded manually via fastboot and it flashes the first couple bits but fails at the bootloader.
Attempting to fastboot boot into twrp returns:
Sending 'boot.img' (38672 KB) OKAY [ 1.412s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
I found the blankflash image for this version of payton, when attempting to run it, the terminal just displays:
< waiting for device >
And nothing ever happens.
I've tried it on Windows and Linux with a handful of different cables and the results are the same. Am I SOL and it's time to replace the device?
Thanks,
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY224H58SP
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 356484080483981
(bootloader) meid:
(bootloader) date: 10-15-2017
(bootloader) sku: XT1900-1
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3899
(bootloader) iccid: 8901260971113779407
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton_fi/payton_sprout:9
(bootloader) ro.build.fingerprint[1]: /PPWS29.69-39-6-13/badd5:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.491.55.payton_fi.
(bootloader) ro.build.version.full[1]: google_fi.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7048.65.01.101R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g097f40be62ed
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.x
(bootloader) kernel.version[2]: 20150123 (prerelease) (GCC) ) #1 SMP PR
(bootloader) kernel.version[3]: EEMPT Thu Sep 24 04:43:29 CDT 2020
(bootloader) git:abl: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) git:xbl: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) gitmic: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) git:rpm: MBM-3.0-payton_fi-f97e5eb-200924
(bootloader) git:tz: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:hyp: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:devcfg: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib64: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:keymaster: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) gitrov: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:storsec: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.047s

Heyyo, blankflash only works if you reboot the device into EDL mode. I can't remember if powering it off, holding down both volume keys and plugging it into a PC will actually boot it into EDL mode or not for Motorola devices though...
You can also try the TinyFastbootScript and see if that works?
Download the ROM from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Download TinyFastbootScript from here which also has the instructions:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work and you can't force reboot to EDL? You can search on Amazon / AliExpress or others for an "Android EDL cable" which can also work to force EDL mode.

ThE_MarD said:
Heyyo, blankflash only works if you reboot the device into EDL mode. I can't remember if powering it off, holding down both volume keys and plugging it into a PC will actually boot it into EDL mode or not for Motorola devices though...
You can also try the TinyFastbootScript and see if that works?
Download the ROM from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Download TinyFastbootScript from here which also has the instructions:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work and you can't force reboot to EDL? You can search on Amazon / AliExpress or others for an "Android EDL cable" which can also work to force EDL mode.
Click to expand...
Click to collapse
Awesome thanks for the reply. Yeah I tried a couple different key combinations that I have seen people reference but nothing seemed to work, however I didn't try holding down both volume keys while plugging it in. I'll try that, and also try the tinyfastboot script too and see what happens. Thanks!

Well I think it's toast. The Tinyfastboot script was giving a lot of the same errors when I was running things manually. I could not get the device to boot into EDL through key combinations either. I think the biggest issue is that the bootloader is locked, and cannot be unlocked. I might try to find a cable and give that a shot but I am thinking now it's a waste of time.
Thanks for the help anyway.

Im facing same issue here as well. so EDL method doesnt work?

moto g9 play flashing_lock and hard brick

The phone is stuck on the Motorola logo screen, then goes to fastboot mode displaying the message "flashing locked". A stock ROM was attempted, but the device does not accept commands and says that the bootloader is locked. When trying to unlock the bootloader, it asks to enable the option in developer mode, but the phone is in hard brick. ADB and recovery attempts were unsuccessful, and it is also not possible to install a custom recovery. All of this happened after attempting to fix a soft brick issue after an update.
It should also be noted that the device had been rooted some time ago and, when turning it on, it was stuck in a bootloop but eventually booted up normally. The root had been undone well before the device was updated.
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-guamp_retail-252ee94a78-220503
(bootloader) product: guamp
(bootloader) board: guamp
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX hC9aP3 RV=08 PV=01 FV=0000000031303030
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5-M8=06 05 00 11
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: ZF5236M8M9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 623C51AB
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804464640
(bootloader) reason: Fall-through from normal boot mode (bootloader) date: 01-07-2021
(bootloader) sku: XT2083-1
(bootloader) carrier_sku: XT2083-1
(bootloader) battid: SB18C44581
(bootloader) battery-voltage: 3849
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/guamp_retail/guamp:11/RPX
(bootloader) ro.build.fingerprint[1]: S31.Q2-58-17-4-8/75835:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-02200-KAMORTA.0
(bootloader) version-baseband: HA10_29.11.02.88R GUAMP_LATAMDSDS_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 Fri A
(bootloader) kernel.version[4]: pr 29 11:24:11 CDT 2022
(bootloader) git:abl: MBM-3.0-guamp_retail-252ee94a78-220503
(bootloader) frp-state: protected (144)
(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) is-userspace: no
(bootloader) pcb-part-no: SB28C98730
(bootloader) primary-display: hlt_ili9882h_video_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.250s
the command returns this
fastboot oem unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.094s

EDL mode returns this
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM8
[ 0.047] Detecting device
[ 34.913] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.913] Check qboot_log.txt for more details
[ 34.913] Total time: 34.929s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error