Database Develop

Unlock bootloader moto x 2014 - XT1097

I recently bought this used cell phone, with android 5.1, I upgraded to the 6 stock (original motorola) but I now want to install a custom ROM, and for this I need to unlock the bootloader, but when I try to do this, this message appears in the command prompt "could Not get unlock data! ", I even tried a crazy on the internet some method to solve but what I found said that I should downgrade and go up rom, but I can not install another rom by RSD lite, I would like a method to be able Do the bootloader unlock and do root, exchange rom these things

roneyss93 said:
I recently bought this used cell phone, with android 5.1, I upgraded to the 6 stock (original motorola) but I now want to install a custom ROM, and for this I need to unlock the bootloader, but when I try to do this, this message appears in the command prompt "could Not get unlock data! ", I even tried a crazy on the internet some method to solve but what I found said that I should downgrade and go up rom, but I can not install another rom by RSD lite, I would like a method to be able Do the bootloader unlock and do root, exchange rom these things
Click to expand...
Click to collapse
You must have the unlock.bin from motorola official site to unlock bootloader.
After send the unlock.bin to your mail you move it to adb folder etc.

papsr6 said:
You must have the unlock.bin from motorola official site to unlock bootloader.
After send the unlock.bin to your mail you move it to adb folder etc.
Click to expand...
Click to collapse
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock

roneyss93 said:
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
Click to expand...
Click to collapse
Did you enable Developer Options by going to Settings, About, tap Build Number 7 times, then go back, enable allow bootloader unlock and Android Debugging.

roneyss93 said:
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
Click to expand...
Click to collapse
Do it again you do something wrong.
I do the same and my fault is the wrong copy of numbers when i copy from commant window.

Gus Ghanem said:
Did you enable Developer Options by going to Settings, About, tap Build Number 7 times, then go back, enable allow bootloader unlock and Android Debugging.
Click to expand...
Click to collapse
I do exactly this, and it continues to give error

papsr6 said:
Do it again you do something wrong.
I do the same and my fault is the wrong copy of numbers when i copy from commant window.
Click to expand...
Click to collapse
I can not even get the numbers that we put on the Motorola site, I have unlocked Motorola before, however this nor give me the codes when I put the command to generate the codes

roneyss93 said:
I do exactly this, and it continues to give error
Click to expand...
Click to collapse
Do this just to get some info, no need to paste it here:
fastboot getvar all
In bootloader mode of course.
EDIT: You can get the latest fastboot and adb from here:
https://developer.android.com/studio/releases/platform-tools.html

Gus Ghanem said:
Do this just to get some info, no need to paste it here:
fastboot getvar all
In bootloader mode of course.
EDIT: You can get the latest fastboot and adb from here:
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Open again the CMD, the most updated according to the link that you sent me. And as a response the commands had this.
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: 6018
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: 0432146139
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: EC13870C0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 353320060936783
(bootloader) meid:
(bootloader) date: 2014-10-24
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jul 5 12:11:27 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retbr/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: br.retbr.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_S
(bootloader) version-baseband[1]: INGLELA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:44:51 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V60.18-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.18-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V60.18-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.18-0-g4ad5029
(bootloader) aboot.git: git=MBM-NG-V60.18-0-g3b3b501
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.229s
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot devices
0432146139 fastboot
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Could not get unlock data!
OKAY [ 0.036s]
finished. total time: 0.036s
D:\Programas\Celular\MOTO X 2\root\platform-tools>
Remember that yes "OEM unlock" and "USB debugging" was enabled. As shown in the image.

Here is mine
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x000E
(bootloader) channelid: 0x80
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-12-2015
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 1 15:55:30 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retca/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: ca.retca.en.CA
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_R
(bootloader) version-baseband[1]: ETCA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:53:00 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: retca
Looks like your bootloader is older, but it shouldn't matter, I think I unlocked mine before the Android 6.0 update, I then relocked it, and unlocked it again a second time. I'm sure a lot of RETBR phones have been unlocked around here. I just can't see what the problem is. But don't try downgrading, you may brick the phone. I don't know what else to suggest. I'm sure you've installed the Motorola USB drivers, but I don't think that's the issue.

Try the Motorola (Lenovo) forums, you can submit your getvar to them, and they will send you an unlock code in a few days:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
Good Luck!
They have forums in Portugese.

Gus Ghanem said:
Here is mine
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x000E
(bootloader) channelid: 0x80
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-12-2015
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 1 15:55:30 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retca/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: ca.retca.en.CA
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_R
(bootloader) version-baseband[1]: ETCA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:53:00 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: retca
Looks like your bootloader is older, but it shouldn't matter, I think I unlocked mine before the Android 6.0 update, I then relocked it, and unlocked it again a second time. I'm sure a lot of RETBR phones have been unlocked around here. I just can't see what the problem is. But don't try downgrading, you may brick the phone. I don't know what else to suggest. I'm sure you've installed the Motorola USB drivers, but I don't think that's the issue.
Click to expand...
Click to collapse
I also do not know what the problem, I even tried to do the downgrade but does not accept any other android pq is not unlocked the bootloader.

HELP !BootLoop after Modem Downgrade HELP!

Hi there XDAs members. I got into big trouble with a Moto E5 XT1921-6 from Verizon Wireless
I unlocked this device a few months ago. But after the Feb 21st 2019 Security patch update, the network was locked again. So I was trying to downgrade (don't laugh please, I give it a shoot) the security patch, I tried to downgrade the Modem, and I made this operations at Fastboot Mode:
Fastboot oem fb_mode_set
Fastboot flash modem NON-HLOS.bin
Fastboot flash gpt gpt.mbn
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot -w
Fastboot fb_mode_clear
But my big mistake is that I installed the modem from a Cricket Firmware accidentally.
And I know that Verizon devices are bootloader locked, so I think this makes worst my situattion.
Before all of this I get the Firmware information of this device:
Code:
XT1921-6
ODPS27.91-121-10-2
ANDROID 8.0.0
1 Feb 2019
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BE.4C
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: ZY323T6CP2
(bootloader) cid: 0x0002
(bootloader) channelid: 0x83
(bootloader) uid: AFB8CEF200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351838095577308
(bootloader) meid:
(bootloader) date: 03-23-2019
(bootloader) sku: XT1921-6
(bootloader) carrier_sku: XT1921-6
(bootloader) battid:
(bootloader) iccid: 89148000004824144474
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 5: 3 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/rjames_vzw_f/rjames_f:8.0
(bootloader) ro.build.fingerprint[1]: .0/ODPS27.91-121-10-2/2:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.286.2.rjames_vzw.
(bootloader) ro.build.version.full[1]: verizon.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8917_21.24.05.68.03R JAMES_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb4405a8 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Fri May 24 17:41:20 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VBE.4C-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=f78e3b0-dirty
(bootloader) devcfg.git: git=f78e3b0-dirty
(bootloader) keymaster.git: git=f78e3b0
(bootloader) cmnlib.git: git=f78e3b0
(bootloader) cmnlib64.git: git=f78e3b0
(bootloader) prov.git: git=f78e3b0-dirty
(bootloader) aboot.git: git=MBM-NG-VBE.4C-0-g992fde4
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: vzw
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
I can't find this Firmware to reinstall it again. I downloaded Firmware Upgrade Utility from Verizon for MOtorola Devices, but I cant Reinstall the firmware. It detects the phone but it doesn't gives me the option to reinstall the firmware.
I was wondering if I get another exactly device, if I can extract via Fastboot this partitions, and reinstall them into my device.
Any idea is welcome :victory:

bullracing said:
Hi there XDAs members. I got into big trouble with a Moto E5 XT1921-6 from Verizon Wireless
I unlocked this device a few months ago. But after the Feb 21st 2019 Security patch update, the network was locked again. So I was trying to downgrade (don't laugh please, I give it a shoot) the security patch, I tried to downgrade the Modem, and I made this operations at Fastboot Mode:
Fastboot oem fb_mode_set
Fastboot flash modem NON-HLOS.bin
Fastboot flash gpt gpt.mbn
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot -w
Fastboot fb_mode_clear
But my big mistake is that I installed the modem from a Cricket Firmware accidentally.
And I know that Verizon devices are bootloader locked, so I think this makes worst my situattion.
Before all of this I get the Firmware information of this device:
Code:
XT1921-6
ODPS27.91-121-10-2
ANDROID 8.0.0
1 Feb 2019
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BE.4C
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: ZY323T6CP2
(bootloader) cid: 0x0002
(bootloader) channelid: 0x83
(bootloader) uid: AFB8CEF200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351838095577308
(bootloader) meid:
(bootloader) date: 03-23-2019
(bootloader) sku: XT1921-6
(bootloader) carrier_sku: XT1921-6
(bootloader) battid:
(bootloader) iccid: 89148000004824144474
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 5: 3 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/rjames_vzw_f/rjames_f:8.0
(bootloader) ro.build.fingerprint[1]: .0/ODPS27.91-121-10-2/2:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.286.2.rjames_vzw.
(bootloader) ro.build.version.full[1]: verizon.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8917_21.24.05.68.03R JAMES_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb4405a8 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Fri May 24 17:41:20 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VBE.4C-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=f78e3b0-dirty
(bootloader) devcfg.git: git=f78e3b0-dirty
(bootloader) keymaster.git: git=f78e3b0
(bootloader) cmnlib.git: git=f78e3b0
(bootloader) cmnlib64.git: git=f78e3b0
(bootloader) prov.git: git=f78e3b0-dirty
(bootloader) aboot.git: git=MBM-NG-VBE.4C-0-g992fde4
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: vzw
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
I can't find this Firmware to reinstall it again. I downloaded Firmware Upgrade Utility from Verizon for MOtorola Devices, but I cant Reinstall the firmware. It detects the phone but it doesn't gives me the option to reinstall the firmware.
I was wondering if I get another exactly device, if I can extract via Fastboot this partitions, and reinstall them into my device.
Any idea is welcome :victory:
Click to expand...
Click to collapse
Use the lenovo/motorola smart assistant to get the necessary firmware for your device. Just do a google search for the program then download it and follow the on screen instructions.
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
mikeshutte said:
Use the lenovo/motorola smart assistant to get the necessary firmware for your device. Just do a google search for the program then download it and follow the on screen instructions.
Click to expand...
Click to collapse
Also here is a link for Moto e5 VZW firmware, https://mirrors.lolinet.com/firmware/moto/rjames/official/VZW/
Should have everything there that you need to fix your device. Good luck

Thanks too much mikeshutte !
okay, I will try first the Lennovo/Moto assistant, if dosent works I will go manually and install the firmware directly from the link.
Really appreciate your Help!

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.

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

I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s

hamhaingaurav said:
I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s
Click to expand...
Click to collapse
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.

riyan65 said:
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.
Click to expand...
Click to collapse
Yes, I knwo there is an hope if i can unlock the bootloader, but the service center guy messed my device, I do not know how they flashed my device, they were flashing my device and said it is not turning on, i said okay return my device, i will flash it my self and after taking from them, i was trying to unlock the bootloader and I was getting the error "Code validation failure with status 7". I am also unable to get Unlock data.
What can i do now, is there any solution to it. Do i need to take my device to service center again ???

Try flashing april stock....then do the OTA update till August..

vivek1310yadav said:
Try flashing april stock....then do the OTA update till August..
Click to expand...
Click to collapse
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.

hamhaingaurav said:
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.
Click to expand...
Click to collapse
PM me..

Baseband not found on Moto X4 Lineage Os 17.1

Good Day! After an unsuccessful attempt to install the Moto X4 rom stock, Now my smartphone does not work the SIM2, only SIM1 and when I start bootloader mod show the message "Baseband <not found>. I know I screwed up using a command at the wrong time, but any command I try to run on fastboot doesn't work. It just says "sending" without finishing the procedure. Several times I execute the commands to try to repair modem1 or modem2 but only an error message appears. The same messages that appeared when I tried to return with the rom stock. can anybody help me? I also tried to install twrp, but I also can't, this device only works with lineage recovery?

wmazoni said:
Good Day! After an unsuccessful attempt to install the Moto X4 rom stock, Now my smartphone does not work the SIM2, only SIM1 and when I start bootloader mod show the message "Baseband <not found>. I know I screwed up using a command at the wrong time, but any command I try to run on fastboot doesn't work. It just says "sending" without finishing the procedure. Several times I execute the commands to try to repair modem1 or modem2 but only an error message appears. The same messages that appeared when I tried to return with the rom stock. can anybody help me? I also tried to install twrp, but I also can't, this device only works with lineage recovery?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-a5ca046-190905
(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: 0043770743
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: E2812B5D
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 359552086827919
(bootloader) meid:
(bootloader) date: 02-02-2018
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4347
(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-a5ca046-190905
(bootloader) git:xbl: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) git:pmic: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190905
(bootloader) git:tz: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:hyp: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:devcfg: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:keymaster: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:prov: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:storsec: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.092s
Hi!!This is the message after you type the command

wmazoni said:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-a5ca046-190905
(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: 0043770743
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: E2812B5D
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 359552086827919
(bootloader) meid:
(bootloader) date: 02-02-2018
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4347
(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-a5ca046-190905
(bootloader) git:xbl: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) git:pmic: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190905
(bootloader) git:tz: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:hyp: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:devcfg: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:keymaster: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:prov: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:storsec: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.092s
Hi!!This is the message after you type the command
Click to expand...
Click to collapse
You are using this firmware?
https://mirrors.lolinet.com/firmware/moto/payton/official/RETBR/
XT1900-6_PAYTON_RETBR_9.0_PPWS29.69-26-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

I am using Lineage OS 17.1. I can t install stock rom on my device. Do you think its work if i try install this firmware?
Enviado de meu Moto X4 usando o Tapatalk

wmazoni said:
I am using Lineage OS 17.1. I can t install stock rom on my device. Do you think its work if i try install this firmware?
Enviado de meu Moto X4 usando o Tapatalk
Click to expand...
Click to collapse
Try just theses from stock version you were using.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my jerry_cheets using XDA Labs

sd_shadow said:
Try just theses from stock version you were using.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my jerry_cheets using XDA Labs
Click to expand...
Click to collapse
In the first command I already get an error message:
https://www.dropbox.com/s/om4mz3us0ers85q/Anotação 2020-09-08 191819.jpg?dl=0

wmazoni said:
Try just theses from stock version you were using.
In the first command I already get an error message:
https://www.dropbox.com/s/om4mz3us0ers85q/Anotação 2020-09-08 191819.jpg?dl=0
Click to expand...
Click to collapse
You may need to change active slot.
Flash
Then change back
Try this to see if slot changes.
Code:
fastboot getvar current-slot
fastboot set_active other
fastboot getvar current-slot
Sent from my ocean using XDA Labs

sd_shadow said:
You may need to change active slot.
Flash
Then change back
Try this to see if slot changes.
Code:
fastboot getvar current-slot
fastboot set_active other
fastboot getvar current-slot
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
The command show active b see the command below pls:
https://www.dropbox.com/s/kebh9oot54o8jqj/Anotação 2020-09-08 224144.jpg?dl=0

wmazoni said:
The command show active b see the command below pls:
https://www.dropbox.com/s/kebh9oot54o8jqj/Anotação 2020-09-08 224144.jpg?dl=0
Click to expand...
Click to collapse
Try changing it to slot a using these commands
https://forum.xda-developers.com/showpost.php?p=71987324&postcount=8
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Try changing it to slot a using these commands
https://forum.xda-developers.com/showpost.php?p=71987324&postcount=8
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi. Now I got to change slot to a.
https://www.dropbox.com/s/2kxb77p5g2...13749.jpg?dl=0
However, I still find an error when I type the following commands, the command does not end:
https://www.dropbox.com/s/e00igqsicq...14453.jpg?dl=0

@sd_shadow, I am running LOS 18.1, without major issue, but my cell signal isn't fantastic. Could just be the chips in the phone, I don't know. I was thinking of flashing the modem from the latest RETUS firmware using your directions from #6. But 1) I think I started off with the stock ROM from a few months earlier and 2) I'd like to not totally screw up my LOS installation. Of course, I can try a backup, but I've never really gotten one restored successfully. Is trying to do this likely to break things?

JimDandy68 said:
@sd_shadow, I am running LOS 18.1, without major issue, but my cell signal isn't fantastic. Could just be the chips in the phone, I don't know. I was thinking of flashing the modem from the latest RETUS firmware using your directions from #6. But 1) I think I started off with the stock ROM from a few months earlier and 2) I'd like to not totally screw up my LOS installation. Of course, I can try a backup, but I've never really gotten one restored successfully. Is trying to do this likely to break things?
Click to expand...
Click to collapse
Just flashing the radio is pretty safe.

sd_shadow said:
Just flashing the radio is pretty safe.
Click to expand...
Click to collapse
Thanks. I suppose I can also reflash from the earlier stock if the most recent causes problems. I'll also be sure to check my slots. Do you flash to both slots or only one?