Database Users

[RUU] 0P9CIMG_A5_DUG_M60_DESIRE_SENSE70_MR_HTC_Europe_3. 12.401.2

0P9CIMG_A5_DUG_M60_DESIRE_SENSE70_MR_HTC_Europe_3.12.401.2_Radio_1.13.3230.27.0617_13.20.3230.00D_F_release_468949_signed_2_4.zip (MARSHMALLOW)
I tested it in my phone. It works smoothly. My new radio (baseband) version is 1.13.3230.27.0617_13.20.3230.00D (Old 1.13.3230.27.0303_13.19.3230.00D)
How to install via fastboot :
- First make sure that your battery is fully charge
- Rename 0P9CIMG_A5_DUG..........zip to 0P9CIMG.zip
- Remove all root from device
- Boot to fastboot
Code:
fastboot devices
fastboot oem rebootRUU
fastboot flash zip 0P9CIMG.zip
fastboot reboot
How to install via Sdcard (I used this) :
- First make sure that your battery is fully charge
- Rename 0P9CIMG_A5_DUG..........zip to 0P9CIMG.zip
- Remove all root from device
- Copy 0P9CIMG.zip to external sdcard
- Restart your mobile into bootloader mode
- It will start the process automatically
Download
androidfilehost
Google Drive

I cannot install this RUU. i tried both method. there is some problem with this zip folder.

sam2351 said:
I cannot install this RUU. i tried both method. there is some problem with this zip folder.
Click to expand...
Click to collapse
- Flash stock recovery
- Re-boot to fastboot
Code:
fastboot devices
fastboot oem lock
and please, try again both method.

ahbecan said:
- Flash stock recovery
- Re-boot to fastboot
Code:
fastboot devices
fastboot oem lock
and please, try again both method.
Click to expand...
Click to collapse
i have tried flashing stock rom first but problem is same.
error: cannot load '0P9CIMG.zip'

sam2351 said:
i have tried flashing stock rom first but problem is same.
error: cannot load '0P9CIMG.zip'
Click to expand...
Click to collapse
Possibilities
- Only rename as 0P9CIMG (or RUU not 0P9CIMG.zip.zip)
- Or RUU file seams to be corrupted
- Or your phone's CID isn't European CID
List of some European CID :
* HTC-Czech HTC__C24
* HTC-Denmark HTC__F08
* HTC-Dutch HTC__E11
* HTC-EastEurope HTC__032
* HTC-FRA HTC__203
* HTC-FRA-Bouygues HTC__247
* HTC-GCC HTC__J15
* HTC-GER HTC__102
* HTC-ITA HTC__405
* HTC-Nor HTC__Y13
* HTC-Norway HTC__H10
* HTC-Poland HTC__B25
* HTC-Russia HTC__A07
* HTC-SPA HTC__304
* HTC-Sweden HTC__G09
* HTC-Turkey HTC__M27
* HTC-WWE HTC__001
Finally, re-boot to fastboot
Code:
Fastboot getvar all
And write here your phone's info

ahbecan said:
Possibilities
- Only rename as 0P9CIMG (or RUU not 0P9CIMG.zip.zip)
- Or RUU file seams to be corrupted
- Or your phone's CID isn't European CID
List of some European CID :
* HTC-Czech HTC__C24
* HTC-Denmark HTC__F08
* HTC-Dutch HTC__E11
* HTC-EastEurope HTC__032
* HTC-FRA HTC__203
* HTC-FRA-Bouygues HTC__247
* HTC-GCC HTC__J15
* HTC-GER HTC__102
* HTC-ITA HTC__405
* HTC-Nor HTC__Y13
* HTC-Norway HTC__H10
* HTC-Poland HTC__B25
* HTC-Russia HTC__A07
* HTC-SPA HTC__304
* HTC-Sweden HTC__G09
* HTC-Turkey HTC__M27
* HTC-WWE HTC__001
Finally, re-boot to fastboot
Code:
Fastboot getvar all
And write here your phone's info
Click to expand...
Click to collapse
Here is my phone info
I renamed only as 0P9CIMG.zip not 0P9CIMG.zip.zip
I think this zip folder is corrupted because when i tried to extract this zip it say corrupted and also i cannot copy this folder to my phone sd card through usb cable.
Here is my phone info
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.13.3230.27.0303
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA4BRWW00***
imei: 352706066556***
imei2: 352706066556***
meid: 00000000000000
product: a5_dug
platform: hTCBmsm8226
modelid: 0P9C70000
cidnum: HTC__J15
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 09813c97
hbootpreupdate: 11
gencheckpt: 0

do u have the marshmallow RUU for A5_UL ?

Ok. You can use this 0P9CIMG.....zip for your phone. You can use micro sd card adapter for copy.
I will upload my file to google drive. EDIT : Google Drive link added in first topic.
sam2351 said:
Here is my phone info
I renamed only as 0P9CIMG.zip not 0P9CIMG.zip.zip
I think this zip folder is corrupted because when i tried to extract this zip it say corrupted and also i cannot copy this folder to my phone sd card through usb cable.
Here is my phone info
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.13.3230.27.0303
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA4BRWW00***
imei: 352706066556***
imei2: 352706066556***
meid: 00000000000000
product: a5_dug
platform: hTCBmsm8226
modelid: 0P9C70000
cidnum: HTC__J15
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 09813c97
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse

https://www.androidfilehost.com/?fid=24438995911967732
shamnath29 said:
do u have the marshmallow RUU for A5_UL ?
Click to expand...
Click to collapse

ahbecan said:
Ok. You can use this 0P9CIMG.....zip for your phone. You can use micro sd card adapter for copy.
I will upload my file to google drive. EDIT : Google Drive link added in first topic.
Click to expand...
Click to collapse
Problem is same
When i tried from sd card it says "device halted due to large image "
And from adb " cant load 0P9CIMG.zip
Sent from my HTC D816w using XDA-Developers mobile app

sam2351 said:
Problem is same
When i tried from sd card it says "device halted due to large image "
And from adb " cant load 0P9CIMG.zip
Sent from my HTC D816w using XDA-Developers mobile app
Click to expand...
Click to collapse
Please, read this guide http://forum.xda-developers.com/showthread.php?t=2952058
Sent from my HTC 816w dual sim with tapatalk.

Will the A5_UL version CID: HTC__039 work here in Philippines?Thanks in advance.
Edit.
Can you also provide the stock recovery for a5_ul Marshmallow. Your help will be deeply appreciated. Im always looking a way to restore my phone to factory stock without the modifications.

stock recovery plllz
Plz...where I can find stock recovery?

husseindara said:
Plz...where I can find stock recovery?
Click to expand...
Click to collapse
Here

All language ? (Vietnamese ?)
Thanks

do u have the stock recovery for A5_DUG

NTPHAT said:
All language ? (Vietnamese ?)
Thanks
Click to expand...
Click to collapse
Sorry, no. But; If you have TWRP, Please use this TWRP backup for Vietnamese after you install this RUU.

thiel1994 said:
do u have the stock recovery for A5_DUG
Click to expand...
Click to collapse
Here ==> [RUU] Desire 816w A5_DUG Marshmallow 6.0 firmware and stock recovery

1. First letter is zero not 'o' 0P9CIMG
2. Check file extension it's .zip,tar,tz, etc ......

Antenna problem
ahbecan said:
0P9CIMG_A5_DUG_M60_DESIRE_SENSE70_MR_HTC_Europe_3.12.401.2_Radio_1.13.3230.27.0617_13.20.3230.00D_F_release_468949_signed_2_4.zip (MARSHMALLOW)
I tested it in my phone. It works smoothly. My new radio (baseband) version is 1.13.3230.27.0617_13.20.3230.00D (Old 1.13.3230.27.0303_13.19.3230.00D)
How to install via fastboot :
- First make sure that your battery is fully charge
- Rename 0P9CIMG_A5_DUG..........zip to 0P9CIMG.zip
- Remove all root from device
- Boot to fastboot
Code:
fastboot devices
fastboot oem rebootRUU
fastboot flash zip 0P9CIMG.zip
fastboot reboot
How to install via Sdcard (I used this) :
- First make sure that your battery is fully charge
- Rename 0P9CIMG_A5_DUG..........zip to 0P9CIMG.zip
- Remove all root from device
- Copy 0P9CIMG.zip to external sdcard
- Restart your mobile into bootloader mode
- It will start the process automatically
hi,My phone is HTC Desire 816 a5dug and when the Android 5 was my device, there was no problem installing and the Internet was always 3G or H+ but since I upgraded to Android 6, the antenna is weakened and the Internet does not change from H.
Is there anyone able to help with this problem? Thanks
Click to expand...
Click to collapse

how to resize recovery partition...please help / dead phone / breaked phone

This questions comes to me and i answer , so if someone could help me in this please :crying::crying::crying:
Rakesh1b said:
answer these questions first?
1.how did you hardbrick your potter?
2.were you updated to latest stock through ota before hardbrick?
3.how did you recover your potter imean what blankflash and gpt.bin,bootloader.img,recovery.img did you use ? the files we all have used or tried from this thread or any different files?
4.type"
fastboot getvar all
Click to expand...
Click to collapse
" in fastboot mode and provide details masking your serial and imei.
5.finally creating blankflash or gpt.bin,bootloader files is impossible,there are some signed images we cant tamper them if we they will not flash.
read this whole thread you will know what im talking about https://forum.xda-developers.com/moto-g4-plus/help/hard-bricked-fastboot-t3638497
Click to expand...
Click to collapse
sir i answer you questions one by one
Question 1 :
i try to upgrade kernal from 7.0 to 7.1 by using this firmware " addison_verizon_oem_vzw_user_7.1.1_NDNS26.118-23-12-3_3_release-keys-cid2_vzw" all command i used are perfect i give you the 2 step info
1) fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.180s]
finished. total time: 0.196s
2) fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.110s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.375s]
finished. total time: 0.484s
Click to expand...
Click to collapse
you see here the gpt.bin pass and bootloader.img pass too
when i reboot the phone bootloader work fine but in logs say : " failed to load kernal"
after that i try to flash the potter firmware " POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info"
i put the problems here
1) fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.094s
2) fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.461s
3) fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.483s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.494s
Click to expand...
Click to collapse
here is the 3 important problem when i try flash the Potter "POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info" and i try others Potter same problem
Question 2 :
It is not ota update
I install TRWP rom and find that i have 16 Mb size in recovery partition and the Potter Recovery.img need 20 Mb
so i use program called Parted to resize the partitions i delete recovery partition and try to make it again but i didn't know his type fat16 or fat36 or linux-swap or ext2 or ext4 .... so and i reboot to bootloader and opppps it is all black
i use blank flash of Moto Z2 play and it back to normal and the problem star the same the partition didn't change
Question 3 :
1) use blankflash of moto z2 play
2) after seeing bootloader run , i install trwp
3)you need to install Debloated+v1 zip here is the link : https://drive.google.com/file/d/12zo_EUgWb4g83t8IjLf9UyFmPGeBx7_G/view
----> copy the zip to phone then install it via TRWP
4) boot to system and it back work normal
Question 4 :
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.07
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2243NCZK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 7B3000D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351859081282935
(bootloader) meid:
(bootloader) date: 04-15-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 11:18: 1 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-92/9:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.281.9.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47R POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4524a37 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT M
(bootloader) kernel.version[3]: on Nov 20 09:32:29 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC1.07-0-g3b15bb0
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=283f623
(bootloader) devcfg.git: git=283f623
(bootloader) keymaster.git: git=283f623
(bootloader) cmnlib.git: git=283f623
(bootloader) cmnlib64.git: git=283f623
(bootloader) prov.git: git=283f623
(bootloader) aboot.git: git=MBM-NG-VC1.07-0-g9d7f987
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
Click to expand...
Click to collapse
here my information
Question 5 :
i know we can't edit or modify gpt.bin and bootloader.img but we can change size partition from recovery mod by trwp but the others people work but at me not , and not that i give you step of what i did
1) adb shell
2) i copy the file parted to sbin
3) chmod +x parted
4) cd /dev/block
5)parted mmcblk0
6) write p
7) here is the partition list
1 131kB 655kB 524kB sbl1
2 655kB 918kB 262kB rpm
3 1180kB 3015kB 1835kB tz
4 3277kB 3342kB 65.5kB devcfg
5 3539kB 5112kB 1573kB aboot
6 5112kB 5374kB 262kB cmnlib
7 5374kB 5636kB 262kB cmnlib64
8 5636kB 5898kB 262kB keymaster
9 5898kB 6095kB 197kB prov
10 6160kB 6685kB 524kB sbl1bak
11 6685kB 6947kB 262kB rpmbak
12 7209kB 9044kB 1835kB tzbak
13 9306kB 9372kB 65.5kB devcfgbak
14 9568kB 11.1MB 1573kB abootbak
15 11.1MB 11.4MB 262kB cmnlibbak
16 11.4MB 11.7MB 262kB cmnlib64bak
17 11.7MB 11.9MB 262kB keymasterbak
18 11.9MB 12.1MB 197kB provbak
19 12.2MB 117MB 105MB ext4 modem
20 117MB 117MB 1024B fsc
21 117MB 117MB 8192B ssd
22 117MB 134MB 16.8MB ext4 dsp
23 134MB 134MB 32.8kB DDR
24 134MB 134MB 16.4kB sec
25 134MB 135MB 524kB utags
26 135MB 135MB 524kB utagsBackup
27 135MB 137MB 2097kB modemst1
28 137MB 139MB 2097kB modemst2
29 139MB 148MB 8389kB fsg
30 148MB 181MB 33.6MB ext4 persist
31 181MB 182MB 524kB frp
32 182MB 182MB 131kB cid
33 182MB 199MB 16.8MB logo
34 199MB 215MB 16.8MB carrier
35 215MB 216MB 524kB metadata
36 216MB 224MB 8389kB kpan
37 224MB 241MB 16.8MB boot
38 241MB 258MB 16.9MB recovery
39 258MB 259MB 1049kB misc
40 259MB 259MB 32.8kB limits
41 259MB 260MB 524kB mota
42 260MB 261MB 1049kB dip
43 261MB 261MB 524kB ext2 syscfg
44 261MB 263MB 2097kB logs
45 263MB 264MB 262kB apdp
46 264MB 264MB 262kB msadp
47 264MB 264MB 8192B dpo
48 264MB 268MB 4325kB padA
49 268MB 277MB 8389kB sp
50 277MB 285MB 8389kB hw
51 285MB 1091MB 805MB ext2 oem
52 1091MB 1359MB 268MB cache
53 1359MB 5654MB 4295MB ext2 system
54 5654MB 31.3GB 25.6GB userdata
Click to expand...
Click to collapse
so when i try to resize the parition recovery it , i deleted oem and recovery partition then i recreated them and add 5 mb to recovery but after i reboot phone got breaked and i use blankflash again and the size of partition didn't change
so if you can help me or contact the admin of the site please i need help to resize the recovery partition
i'm new here in this forum

bro your problem might be wrong formatted system and cache. see the above lines 51 285MB 1091MB 805MB ext2 oem---it should be ext4
52 1091MB 1359MB 268MB cache
53 1359MB 5654MB 4295MB ext2 system---it should be ext4
54 5654MB 31.3GB 25.6GB userdata it should be f2fs type formatted
may be you formatted your system partitions with wrong format type.
bro then try this type "fastboot erase all" it erases everything then do as i say once
1.flash "fastboot flash partition gpt.bin" (file to be used that you had used above the file of motoz play one https://drive.google.com/open?id=0B7X6bQHmiX_BY29Damx5ejEyX1U)
2.flash "fastboot flash bootloader bootloader.img"(file in the above given link)
3.flash "fastboot flash recovery recovery.img"(in the above link the files are there)
reboot bootloader then go to recovery mode it shows android error symbol then press power and then vol up then erase data,cache,and mount system then reboot to bootloader now flash "fastboot flash recovery twrp(latest 64bit) link http://moto-roms.netlib.re/twrp-3.2.1-1-potter.img
then see if boots to recovery if it went to recovery then wipe everything and do advanced wipe wipe cache ,system with ext4 format type and data with f2fs type format individually and now erase all items selected in the advanced wipe menu and factory reset then reboot to recovery and now copy the latest debloated stock rom or twrp flashable stock link https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
then flash it.
boot into os once evrything working fine now you can move to any custom rom .
TIP:i dont know if you have previous twrp backup of efs but if you have you are safe save a efs copy once every thing works fine.
ALL THE BEST.

Rakesh1b said:
bro your problem might be wrong formatted system and cache. see the above lines 51 285MB 1091MB 805MB ext2 oem---it should be ext4
52 1091MB 1359MB 268MB cache
53 1359MB 5654MB 4295MB ext2 system---it should be ext4
54 5654MB 31.3GB 25.6GB userdata it should be f2fs type formatted
may be you formatted your system partitions with wrong format type.
bro then try this type "fastboot erase all" it erases everything then do as i say once
1.flash "fastboot flash partition gpt.bin" (file to be used that you had used above the file of motoz play one https://drive.google.com/open?id=0B7X6bQHmiX_BY29Damx5ejEyX1U)
2.flash "fastboot flash bootloader bootloader.img"(file in the above given link)
3.flash "fastboot flash recovery recovery.img"(in the above link the files are there)
reboot bootloader then go to recovery mode it shows android error symbol then press power and then vol up then erase data,cache,and mount system then reboot to bootloader now flash "fastboot flash recovery twrp(latest 64bit) link http://moto-roms.netlib.re/twrp-3.2.1-1-potter.img
then see if boots to recovery if it went to recovery then wipe everything and do advanced wipe wipe cache ,system with ext4 format type and data with f2fs type format individually and now erase all items selected in the advanced wipe menu and factory reset then reboot to recovery and now copy the latest debloated stock rom or twrp flashable stock link https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
then flash it.
boot into os once evrything working fine now you can move to any custom rom .
TIP:i dont know if you have previous twrp backup of efs but if you have you are safe save a efs copy once every thing works fine.
ALL THE BEST.
Click to expand...
Click to collapse
Sorry bro but this not what i ask for , i asked for changeing partitions , this is all i done it and it work well all i need is to change partition recovery, and why moto g5 plus stay in deep freeze , i use gdisk and delete partition system and recreate it but after i reboot the phone everythink back old , the kernel didn't change anythink , why it happen to me , i need to resize the partitions , the gpt.bin i flashed are wrong... it steal 2 gb from my memory and put recovery partition size 16M this is not good bro, we should find way to change partitions , if you know any phone motorola can change partition link it to me , cause this is all phones motorola happen

I'm unable to unlock my qualified for unlocking Moto g4 plus

Hey, I am not able to unlock the bootloader of the Moto g4 plus. The cid is 0x0000. I am on stock nougat 7.0 with the April 2018 security patch. If I need to send more info, feel free to ask.

rick kode said:
Hey, I am not able to unlock the bootloader of the Moto g4 plus. The cid is 0x0000. I am on stock nougat 7.0 with the April 2018 security patch. If I need to send more info, feel free to ask.
Click to expand...
Click to collapse
Did you followed this guide https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584 ?

strongst said:
Did you followed this guide https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584 ?
Click to expand...
Click to collapse
Yes I have followed that guide, I have tried it multiple times

rick kode said:
Yes I have followed that guide, I have tried it multiple times
Click to expand...
Click to collapse
Where in the process is your unlocking attempt failing? Is it getting the unlock code from your device or requesting the code from Motorola?
Can we see your getvar info?
1) reboot your device to the bootloader. Connect your device to your computer via USB.
2) open an ADB terminal. In the ADB terminal, type 'fastboot getvar all' without the quotes. Press enter. You should get a list of variables about your device.
3) please post or upload the details here, you may wish to omit your IMEI.

echo92 said:
Where in the process is your unlocking attempt failing? Is it getting the unlock code from your device or requesting the code from Motorola?
Can we see your getvar info?
1) reboot your device to the bootloader. Connect your device to your computer via USB.
2) open an ADB terminal. In the ADB terminal, type 'fastboot getvar all' without the quotes. Press enter. You should get a list of variables about your device.
3) please post or upload the details here, you may wish to omit your IMEI.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2239XJQJ
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 1A8BC10000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (i deleted this)
(bootloader) meid:
(bootloader) date: 06-13-2016
(bootloader) sku: XT1642
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Mar 1 0: 9:19 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.02R ATHENE_EMEA_D
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-ge03508d-00131-g44
(bootloader) kernel.version[1]: 2576f ([email protected]) (gcc version
(bootloader) kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version[3]: :58:16 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (210)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.085s

C:\Users\RickK\Downloads\mfastboot-v2\mfastboot-v2>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.105s]
finished. total time: 0.107s
and this is the result from trying to get the code

rick kode said:
C:\Users\RickK\Downloads\mfastboot-v2\mfastboot-v2>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.105s]
finished. total time: 0.107s
and this is the result from trying to get the code
Click to expand...
Click to collapse
Hmm, thanks for that - looks like there's an issue with your device - looking at the getvar info, there's no carrier listed ((bootloader) ro.carrier: unknown ). What software channel is listed on your device under Settings>About Phone?
You may wish to submit the unlock data information and getvar info (including IMEI) to the official Motorola forums: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809 Please follow the instructions on that thread, and provide all the information they request. Hopefully they can generate an unlock code for you, but please bear in mind they request at least 2 business days once the request is forwarded.

My software channel is reteu, it can Be true that I don't have a carrier, I bought this device stand alone and later put the Sim in. I will see what they can do at the official forums

rick kode said:
My software channel is reteu, it can Be true that I don't have a carrier, I bought this device stand alone and later put the Sim in. I will see what they can do at the official forums
Click to expand...
Click to collapse
In that case, that entry in the getvar info should show up as reteu, regardless of if you bought the device standalone. For example, my device was bought direct from Motorola, no phone carrier involved and it reports retgb as the carrier.
Code:
(bootloader) current-time: "Tue Jun 16 22:51:38 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.02R ATHENE_EMEA_D
(bootloader) version-baseband[1]: SDS_CUST
<snip>
(bootloader) frp-state: protected (77)
[B](bootloader) ro.carrier: retgb[/B]
I'd consult the Motorola forum thread on the issue, they may be able to generate a code for you or ask you to submit your device for service.

Okay, thanks for the help! I'll check the forum!

Htc U ULTRA ROM HELP

#Detecting device
Connected mode ... [fastboot]
Reading information ... [ok]
product : ?
version main : ?
version bootloader : ?
version : 0.5
serialno : FA81A1700519
imei : ?
platform : ?
cidnum : ?
modelid : ?
security : ?
battery status : ?
battery voltage : ?
build mode : ?
partition layout : ?
version-baseband : ?
#Reading Identifier Token
Detecting device ... [ok]
Wait for device ... [ok]
Reading Token ... [fail]
NO RECOVERY NO OS PLS:crying:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xdbf000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xdc000000
(bootloader) serialno:FA81A1700519
all:

Moto X4 (XT1900-7) - no unlockdata for bootloader

Hi Guys,
I´m stuck with a tricky problem, may someone can help/has an idea how to fix that.
My Moto X4 has no unlock data, I was also in contact with the lenovo support.
The reply of the lenovo support was:
"Sorry for the late reply. The team I endorsed this with told me that the phone cannot be unlocked. We don't know the reason for sure, but it's possible that unlock data block has gone missing, is corrupt, or has not been programmed into the device."
last option(may)
"You can try checking in the service center and reflash the phone, but I can't guarantee anything. Thanks."
Phone data:
fastboot oem get_unlock_data
(bootloader) Failed to get unlock data.
OKAY [ 0.007s]
Finished. Total time: 0.007s
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(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: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4140
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.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: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.040s
So I tried first the recovery with the lenovo software (rescue_and_smart_assistant_v5.6.0.15),
fixed nothing.
So google gave me no hint how to "crack" the bootloader... does someone know how I could unlock the bootloader anyway,
I don´t care if i may break the phone, if it´s stuck in Android 9 it´s useless. I already upgraded to Moto Edge (G100).
Just want to use it as fallback phone.
Bests Marc

spacewan said:
Hi Guys,
I´m stuck with a tricky problem, may someone can help/has an idea how to fix that.
My Moto X4 has no unlock data, I was also in contact with the lenovo support.
The reply of the lenovo support was:
"Sorry for the late reply. The team I endorsed this with told me that the phone cannot be unlocked. We don't know the reason for sure, but it's possible that unlock data block has gone missing, is corrupt, or has not been programmed into the device."
last option(may)
"You can try checking in the service center and reflash the phone, but I can't guarantee anything. Thanks."
Phone data:
fastboot oem get_unlock_data
(bootloader) Failed to get unlock data.
OKAY [ 0.007s]
Finished. Total time: 0.007s
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(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: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4140
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.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: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.040s
So I tried first the recovery with the lenovo software (rescue_and_smart_assistant_v5.6.0.15),
fixed nothing.
So google gave me no hint how to "crack" the bootloader... does someone know how I could unlock the bootloader anyway,
I don´t care if i may break the phone, if it´s stuck in Android 9 it´s useless. I already upgraded to Moto Edge (G100).
Just want to use it as fallback phone.
Bests Marc
Click to expand...
Click to collapse
You have an X4 so next time you should post in the X4 forum
https://forum.xda-developers.com/c/moto-x4.6912/
Well, looking at the getvar all it's not good.
XT1900-7 could be DTPL(TMO), Playpl, or RetEU
Cid 0x0000 cannot be unlocked
Code:
(bootloader) cid: 0x0000
You might be able to flash the stock firmware.
Looks like it's on the latest version
PPWS29.69-37-5
If you know which Carrier/software channel it was on download the firmware from
https://mirrors.lolinet.com/firmware/moto/payton/official/
If you have an old Windows 7 or XP machine use RSD Lite, that is your best option, it doesn't work on Windows 9/10.
If that's not an option use fastboot.exe or mfastboot
and flash this from Firmware
Code:
fastboot flash partition gpt.bin
If it's the firmware and it flashes successfully, Getvar all should have more info
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

sd_shadow said:
You have an X4 so next time you should post in the X4 forum
https://forum.xda-developers.com/c/moto-x4.6912/
Click to expand...
Click to collapse
I´m sorry, haven´ t seen it... @Admin... could you may move it?
sd_shadow said:
Well, looking at the getvar all it's not good.
XT1900-7 could be DTPL(TMO), Playpl, or RetEU
Click to expand...
Click to collapse
I´m almost sure that it´s the RetEU one
sd_shadow said:
Cid 0x0000 cannot be unlocked
Code:
(bootloader) cid: 0x0000
You might be able to flash the stock firmware.
Looks like it's on the latest version
PPWS29.69-37-5
If you know which Carrier/software channel it was on download the firmware from
https://mirrors.lolinet.com/firmware/moto/payton/official/
Click to expand...
Click to collapse
Thanks for this link I´ll gonna check. I´m using Vodafone, but the Phone is not branded.
sd_shadow said:
If you have an old Windows 7 or XP machine use RSD Lite, that is your best option, it doesn't work on Windows 9/10.
Click to expand...
Click to collapse
No I only have Win 10, but only for "emergency", I´m using generally a linux desktop,
so I gonna try it with fastboot of the adb-tools
sd_shadow said:
If that's not an option use fastboot.exe or mfastboot
and flash this from Firmware
Code:
fastboot flash partition gpt.bin
If it's the firmware and it flashes successfully, Getvar all should have more info
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
I´ll try that during the next days, let´s see what happens, thanks so far.
Bests Marc

HI Shadow,
made it (used XT1900-7_PAYTON_RETEU_DS_9.0_PPWS29.69-37-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
, this was the output:
[email protected]:/home/moto-x4# fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
Sending 'partition' (37 KB)...
OKAY [ 0.001s]
Writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.112s]
Finished. Total time: 0.114s
[email protected]:/home/moto-x4# fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(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: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4264
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.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: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.048s
I see as quick view that the slot switched from b to a, may have have to specify the slot during the falsh as well?
Bests Marc

I was impatient, so I flashed everything, now the phone is (as may expected) stuck in a bootloop.
output is:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(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: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(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: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4246
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.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: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(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: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.041s
I´m wondering why fastboot set_active a/b is not working, get the message FAILED (remote failure).
Bests Marc

Ok, got it running again with recovering about the original LMSA Software.
Now it says:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(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: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4275
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.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: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.048s
Again from the beginning...how to kill/crack this damn locked bootloader without oem_unlock_data...
I want to get a custom rom on it.
Bests Marc