BL: MBM-3.0-payton_retail-0e6e7ce-181231 - Moto X4 Questions & Answers

Hi Everyone have a stock rom of moto x4 whit this version of bootloader?
Code:
BL: MBM-3.0-payton_retail-0e6e7ce-181231
I download all retail stock roms on lolinet, around 80gb of stock roms for x4 and all have other BL versions...
The PPWS29.69-26-4 have this MBM Version: MBM-3.0-payton_retail-6b0c3d7-181231
But 6b0c3d7 i need whit 0e6e7ce because all the sotck roms say (Bootloader) Permison denied
My x4 dont have system to boot and have bootloader locked, only can flash the stock rom whit same bootloader version

llue45 said:
Hi Everyone have a stock rom of moto x4 whit this version of bootloader?
Code:
BL: MBM-3.0-payton_retail-0e6e7ce-181231
I download all retail stock roms on lolinet, around 80gb of stock roms for x4 and all have other BL versions...
The PPWS29.69-26-4 have this MBM Version: MBM-3.0-payton_retail-6b0c3d7-181231
But 6b0c3d7 i need whit 0e6e7ce because all the sotck roms say (Bootloader) Permison denied
My x4 dont have system to boot and have bootloader locked, only can flash the stock rom whit same bootloader version
Click to expand...
Click to collapse
I will jump in here briefly. You may be getting the bootloader error because your phone has a 9 bootloader and you are trying to flash it with an 8 or 7 bootloader. I am assuming your phone was Amazon, yes?
In lolinet moto/payton/official/AMZ I see:
file "XT1900-1_PAYTON_AMZ_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2019-01-16 13:03 2263643 KB"
Have you tried that?
If not Amazon, do not try that but reply back.

KrisM22 said:
I will jump in here briefly. You may be getting the bootloader error because your phone has a 9 bootloader and you are trying to flash it with an 8 or 7 bootloader. I am assuming your phone was Amazon, yes?
In lolinet moto/payton/official/AMZ I see:
file "XT1900-1_PAYTON_AMZ_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2019-01-16 13:03 2263643 KB"
Have you tried that?
If not Amazon, do not try that but reply back.
Click to expand...
Click to collapse
i have the PPW29.69-26 retail, the bootloader is the same between retail and amz version and i try with that, the result is the same (Bootloader) Permison denied...
Code:
BUILD REQUEST INFO:
SW Version: payton-user 9 PPW29.69-26 7a8e1 release-keysM660_7042.27.01.89R
MBM Version: MBM-3.0-payton_retail-6b0c3d7-181117
Modem Version: M660_7042.27.01.89R
FSG Version: FSG-660-01.95
Build Fingerprint: motorola/payton/payton:9/PPW29.69-26/7a8e1:user/release-keys
CQATest App Version: 6.0.4
My moto x4 isnt amz is openmx...My getvar is
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-181231
(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: ZY224QT2VT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x29
(bootloader) uid: AB7DEE02
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 356486081004948
(bootloader) meid:
(bootloader) date: 01-11-2018
(bootloader) sku: XT1900-4
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3846
(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]: -26-4/a2a2:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.211.11.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-g6448940 (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]: Mon Dec 31 10:17:24 CST 2018
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-181231
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-181231
(bootloader) git:pmic: MBM-3.0-payton_retail-6b0c3d7-181231
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-181231
(bootloader) git:tz: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:hyp: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:devcfg: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:cmnlib: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:keymaster: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:prov: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:storsec: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: openmx
(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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 5.939s

Okay. 1900-4
unlocked at motorola
flashed lineage 16
erased system
locked the phone but without a system???????? how?
and when you try to unlock the phone again as you did first, what happens?
You got the 2 sets of code above by doing what? booting to bootloader, connecting to PC and issuing what commands?
Could you give me a picture of your bootloader screen. Thanks.
I notice looking at lineage 16 in X4 ROMs, that though it is based on pie (9), the OP on that thread says it is based on Oreo 8.1
Assuming that is correct, you couldn't have a Pie bootloader, but an Oreo bootloader (?) But your getvar says 29.69 which is Pie.
(confused!) but let me have pic of your bootloader screen please.
EDIT: You said"...all ok...but i erase all the system and by mistake i reunlock the bootloader but whitout system...
I cant start sistem because not exist! I cant reflash because bootloader is lock..."
When you issued that "lock" what ROM were you trying to flash? what ROM was present in that flash? Did that flash change the bootloader?

KrisM22 said:
Okay. 1900-4
unlocked at motorola
flashed lineage 16
erased system
locked the phone but without a system???????? how?
and when you try to unlock the phone again as you did first, what happens?
You got the 2 sets of code above by doing what? booting to bootloader, connecting to PC and issuing what commands?
Could you give me a picture of your bootloader screen. Thanks.
I notice looking at lineage 16 in X4 ROMs, that though it is based on pie (9), the OP on that thread says it is based on Oreo 8.1
Assuming that is correct, you couldn't have a Pie bootloader, but an Oreo bootloader (?) But your getvar says 29.69 which is Pie.
(confused!) but let me have pic of your bootloader screen please.
EDIT: You said"...all ok...but i erase all the system and by mistake i reunlock the bootloader but whitout system...
I cant start sistem because not exist! I cant reflash because bootloader is lock..."
When you issued that "lock" what ROM were you trying to flash? what ROM was present in that flash? Did that flash change the bootloader?
Click to expand...
Click to collapse
Hi bro, sorry, i have a time without internet access...
1.-
Code:
locked the phone but without a system???????? how?
First i erase the partitions in twrp because i want a clean instalation, after this i unlock the bootloader runing the wrong code "fastboot lock oem", for that reason i have bootloader locked and not android system...
2.-
Code:
and when you try to unlock the phone again as you did first, what happens?
it say "enable OEM unlocking on Android"
I need enter to android and in developer options active oem unlock...But i dont have android system...
3.-
Could you give me a picture of your bootloader screen. Thanks.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4.-
Code:
When you issued that "lock" what ROM were you trying to flash? what ROM was present in that flash? Did that flash change the bootloader?
I lock the bootloader before try to flash, before to erase the system i have lineage OS 16

llue45 said:
Hi bro, sorry, i have a time without internet access...
...snip...
4.-
Code:
When you issued that "lock" what ROM were you trying to flash? what ROM was present in that flash? Did that flash change the bootloader?
I lock the bootloader before try to flash, before to erase the system i have lineage OS 16
Click to expand...
Click to collapse
Thanks. Sorry if repeat, but I am confused.
You "locked the bootloader", or, it WAS locked since you never unlocked it. Or did you at one point have it unlocked?
How did you manage to lock it???
Thanks.

KrisM22 said:
Thanks. Sorry if repeat, but I am confused.
You "locked the bootloader", or, it WAS locked since you never unlocked it. Or did you at one point have it unlocked?
How did you manage to lock it???
Thanks.
Click to expand...
Click to collapse
I locked the bootloader after unlock...
I do this...
1.-Unlock Bootloader
2.-Flash TWRP
3.-FLASH LINEAGE OS 16
4.-ERASE SYSTEM FORMATING PARTITIONS
5.-LOCK BOOTLOADER WITH COMAND "fastboot oem lock"
6.-Im stupid guy ... i know
In just five hours i destroy my new moto x4

llue45 said:
...snip...
Click to expand...
Click to collapse
llue45 said:
I locked the bootloader after unlock...
I do this...
1.-Unlock Bootloader
2.-Flash TWRP
3.-FLASH LINEAGE OS 16
4.-ERASE SYSTEM FORMATING PARTITIONS
5.-LOCK BOOTLOADER WITH COMAND "fastboot oem lock"
6.-Im stupid guy ... i know
In just five hours i destroy my new moto x4
Click to expand...
Click to collapse
I was afraid of that. I have no idea. If sd_shadow's thoughts don't help, I guess send it back to Moto to be factory reset. Sorry.
Been seeing too many folks waylaid by lineage; and re-locking bootloader.
:crying:

KrisM22 said:
I was afraid of that. I have no idea. If sd_shadow's thoughts don't help, I guess send it back to Moto to be factory reset. Sorry.
Been seeing too many folks waylaid by lineage; and re-locking bootloader.
:crying:
Click to expand...
Click to collapse
Thanks for all your support bro You are an excellent person

The real problem is folks, who should know better, posting bat files with that lock command, and noobs coming along and using them.
---------- Post added at 05:30 PM ---------- Previous post was at 05:14 PM ----------
llue45 said:
Thanks for all your support bro You are an excellent person
Click to expand...
Click to collapse
You're welcome - wish I could have helped.

hello when this happens you need to look for the rom with the VPN activated, because it is not the same in your country. If the BL is not the same, the rom does not pass.

Related

[XT1097 AT&T] Last Time Flashing Failed Bootloop

Well.. I may have messed up beyond belief.
I accidentally ordered the AT&T variant instead of going with XT1095, and instead of returning it, I figured I'd unlock it and convert.
To my error, I tried CF-Auto-Root-victara-victararetbr-xt1097 with a locked bootloader and I was put into a bootloop with the error "Fastboot Reason: Last time flashing failed"
Am I screwed? Are there ways to fix this new $325 brick?
I just remembered, I have my old XT1095 IMEI and bootloader code. Is there anyway to flash my XT1097 with those numbers so my phone can pretend to be my old 'Pure' edition and be able to unlocked?
Have you check unlocking the bootloader from motorola site? I heared xt1097 is also unlocking now via motorola website, you can also try these lines hope it will help you reboot in fastboot first then type these:
Fastboot reboot-bootloader
Fastboot oem fb_mode_set
Fastboot erase cache
Fastboot oem fb_mode_clear
Fastboot reboot
Hope you will get the device back running.. If these didnt help kindly get back here.. And dont try any imei tweak etc you will hard brick that
Salik Iqbal said:
Have you check unlocking the bootloader from motorola site? I heared xt1097 is also unlocking now via motorola website, you can also try these lines hope it will help you reboot in fastboot first then type these:
Fastboot reboot-bootloader
Fastboot oem fb_mode_set
Fastboot erase cache
Fastboot oem fb_mode_clear
Fastboot reboot
Hope you will get the device back running.. If these didnt help kindly get back here.. And dont try any imei tweak etc you will hard brick that
Click to expand...
Click to collapse
I've tried what you posted to no avail.
I've been trying to download VICTARA_ATT_XT1097_5.1_LPE23.32-21.9_cid1_CFC.xml.zip or VICTARA_ATT_XT1097_5.1_LPE23.32-21.2_cid1_CFC.xml.zip from FileFactory, but because i'm using the "Slow Speed" download(50Kb/s), it keeps failing, so I haven't even been able to try flashing the official ATT Victara firmware.
I'm almost positive it's because the partition was flashed over... so I'm hoping if I can get one of these files downloaded, I can try flashing the original gpt.bin and it boot fine..
Any other ideas would be extremely helpful.
If this helps, this is all the info from my bootloader
AP Fastboot Flash Mode (S)
60.16 (sha-496ce05,c2015-04-02 18:55:00)
CPU: MSM8974AC ES1.1
eMMC: 32GB Samsung RV=07 PV=0B TY=57
DRAM: 2048MB Elpida S8 SDRAM DIE=4GB
Battery OK
Device is LOCKED. Status Code: 0
Software status: Official
Fastboot getvar all
Paste the output pls
Salik Iqbal said:
Fastboot getvar all
Paste the output pls
Click to expand...
Click to collapse
I just need VICTARA_ATT_XT1097_5.1_LPE_23.32-21.9 gpt.bin if I do belive so myself. Teach me if i'm wrong, I truly am interested in learning this stuff!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(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: TA449074CQ
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 6FD5BD0D0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***************
(bootloader) meid:
(bootloader) date: 02-11-2016
(bootloader) sku: XT1097
(bootloader) iccid:********************
(bootloader) cust_md5: ********************************
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jun 28 20:20:35 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/victara_att/victara:5.1/L
(bootloader) ro.build.fingerprint[1]: PE23.32-21.9/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.16.9.victara_att.
(bootloader) ro.build.version.full[1]: att.en.US
(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_4235210.110.09.11R VICTARA_A
(bootloader) version-baseband[1]: TT_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-gff6f5d9 ([email protected]
(bootloader) kernel.version[1]: ilclbld32) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Sep 29 04:22:36 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: att
all: listed above
finished. total time: 0.101s
you need full flash, not just gpt.bin.. if you did flashing this gpt only, you will have dead bricked device.. check the pvt msg i gave you fast download link there.. download rsd lite, unzip that and flash the full stock rom.. good luck!
Salik Iqbal said:
you need full flash, not just gpt.bin.. if you did flashing this gpt only, you will have dead bricked device.. check the pvt msg i gave you fast download link there.. download rsd lite, unzip that and flash the full stock rom.. good luck!
Click to expand...
Click to collapse
THANK YOU! I really appreciate it, you have no idea how happy I am.
RSD Lite and fastboot, gives me the error: version downgraded for primary_gpt.
ibphantom said:
THANK YOU! I really appreciate it, you have no idea how happy I am.
RSD Lite and fastboot, gives me the error: version downgraded for primary_gpt.
Click to expand...
Click to collapse
It was latest that i gave you..
Salik Iqbal said:
It was latest that i gave you..
Click to expand...
Click to collapse
Uhh... so what could the problem be? lol.
ibphantom said:
THANK YOU! I really appreciate it, you have no idea how happy I am.
RSD Lite and fastboot, gives me the error: version downgraded for primary_gpt.
Click to expand...
Click to collapse
There are other att files on that folder, download and check if they work for you.. Also edit the xml abd remove two lines gpt.bin and motoboot.img start it with boot.img
Salik Iqbal said:
There are other att files on that folder, download and check if they work for you.. Also edit the xml abd remove two lines gpt.bin and motoboot.img start it with boot.img
Click to expand...
Click to collapse
I removed
<step MD5="72167323145a532c1158c13f8543e6d3" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="a942904bb71a2ba69c27a440e1f9801e" filename="motoboot.img" operation="flash" partition="motoboot"/>
and it flashed up to the boot.img
I got another 'Version Downgraded' error for boot
Does it matter that my bootloader CPU is MSM8974AC ES1.1 and the release keys are for MSM8974BP_4235210.110.09.11R?
I have same problem please somehow help me too
I can't flash boot.img
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA98901CI9
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: F9FED40C0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 359279050697553
(bootloader) meid:
(bootloader) date: 09-16-2014
(bootloader) sku: XT1097
(bootloader) iccid: 89014103286416801740
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 22 11:45:36 UTC 2016"
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gff6f5d9 ([email protected]
(bootloader) kernel.version[1]: ilclbld32) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Sep 29 04:22:36 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: att
all: listed above
finished. total time: 0.092s
Click to expand...
Click to collapse
MrSaba said:
I have same problem please somehow help me too
I can't flash boot.img
Click to expand...
Click to collapse
Does anybody know how to erase the gpt.bin so that I can flash stock?
I flashed from XT1095 gpt.bin and now I get the "Version Downgraded for primary_gpt" error.
ibphantom said:
Does anybody know how to erase the gpt.bin so that I can flash stock?
I flashed from XT1095 gpt.bin and now I get the "Version Downgraded for primary_gpt" error.
Click to expand...
Click to collapse
Is your bootloader locked? It must be unlocked to flash firmware from other models as well as to downgrade.
Sent from my XT1095 using Tapatalk
AGISCI said:
Is your bootloader locked? It must be unlocked to flash firmware from other models as well as to downgrade.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Yeah, it's locked. I was just asking in hope that someone had a work around.
I guess I'll try to ship it back to Motorola(since it's within 14 days) and pretend I never even turned it on and ask for the PURE as a replacement.
ibphantom said:
Yeah, it's locked. I was just asking in hope that someone had a work around.
I guess I'll try to ship it back to Motorola(since it's within 14 days) and pretend I never even turned it on and ask for the PURE as a replacement.
Click to expand...
Click to collapse
Yeah, there is nothing you can do. Never flash anything with a locked bootloader, it's a recipe for disaster.
Sent from my XT1095 using Tapatalk
ibphantom said:
Does anybody know how to erase the gpt.bin so that I can flash stock?
I flashed from XT1095 gpt.bin and now I get the "Version Downgraded for primary_gpt" error.
Click to expand...
Click to collapse
Dont play with gpt.bin mate.. You will brick your phone, just wait a little bit more Marshmallow is comming soon, you will have your device working soon, dont try other variant gpt partitions you will brick your phone..
---------- Post added at 11:02 PM ---------- Previous post was at 10:51 PM ----------
Salik Iqbal said:
Dont play with gpt.bin mate.. You will brick your phone, just wait a little bit more Marshmallow is comming soon, you will have your device working soon, dont try other variant gpt partitions you will brick your phone..
Click to expand...
Click to collapse
Umm i found something stupid in your fastboot getvar :/ can you please try this:
Fastboot reboot-bootloader
Fastboot oem fb_mode_clear
Fastboot reboot
softbrick?
I have the same problem, i have XT1097 AT&T and i flashed other provider XT1097 Rom and i cant power on my device i only show fastboot mode and the error to downgrade bootloader , i do not know how can i return to stock , can anyone tell me what can i do ?

XT1926-6 Your device is corrupt

Hi, I have a Motorola g6 xt1926-6, with a leyend “your device is corrupt” I try to upload so many softwares but it show me only error, the device have lock the bootloader
I need help me please
yxmikx said:
Hi, I have a Motorola g6 xt1926-6, with a leyend “your device is corrupt” I try to upload so many softwares but it show me only error, the device have lock the bootloader
I need help me please
Click to expand...
Click to collapse
Unlock the bootloader on the Motorola website, take the steps, and once unlocked when you flash the factory firmware you will be installed
Enviado desde mi moto g(6) mediante Tapatalk
stifmaster81 said:
Unlock the bootloader on the Motorola website, take the steps, and once unlocked when you flash the factory firmware you will be installed
Enviado desde mi moto g(6) mediante Tapatalk
Click to expand...
Click to collapse
I can not enter the system to activate the oem option, that's why I have not unlocked
yxmikx said:
I can not enter the system to activate the oem option, that's why I have not unlocked
Click to expand...
Click to collapse
your Motorola goes into recovery?
Power More volume less?
Enviado desde mi moto g(6) mediante Tapatalk
yxmikx said:
I can not enter the system to activate the oem option, that's why I have not unlocked
Click to expand...
Click to collapse
Hmm, can you remember what firmware you had? Have you tried booting to recovery and tried a cache wipe or factory reset?
If your bootloader is still locked and you did not request an unlock key from Motorola, it might be worth considering visiting a service centre and getting your device looked at. You've still got the warranty, hopefully - might as well use it...
yxmikx said:
I can not enter the system to activate the oem option, that's why I have not unlocked
Click to expand...
Click to collapse
You don't need to enter the system. Hold Volume Down and the power button then follow the steps to flash your stock firmware. You need fastboot.exe on your pc. Plug in a USB cable to the pc and phone then flash the stock firmware. Make sure when you power on the device using power + Vol Down to unlock your bootloader. The option you refer to in system does nothing on its own.
Also tell us how you ended up in this situation. I'm guessing you did something to cause the problem?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
You don't need to enter the system. Hold Volume Down and the power button then follow the steps to flash your stock firmware. You need fastboot.exe on your pc. Plug in a USB cable to the pc and phone then flash the stock firmware. Make sure when you power on the device using power + Vol Down to unlock your bootloader. The option you refer to in system does nothing on its own.
Also tell us how you ended up in this situation. I'm guessing you did something to cause the problem?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
I believe you need the bootloader unlocked in order to flash anything. I have a 1926-7 and I'm stuck in bootloader, since I can't access the operating system to allow Developer Options, I can't unlock bootloader, and my os is corrupt.
What can I do? Thanks
DavCan said:
I believe you need the bootloader unlocked in order to flash anything. I have a 1926-7 and I'm stuck in bootloader, since I can't access the operating system to allow Developer Options, I can't unlock bootloader, and my os is corrupt.
What can I do? Thanks
Click to expand...
Click to collapse
You should be able to flash official Moto firmware whether your bootloader is unlocked or not.
Look here:
https://mirrors.lolinet.com/firmware/moto/evert/official/
Download the correct firmware for your device and flash.
Ragarianok said:
You should be able to flash official Moto firmware whether your bootloader is unlocked or not.
Look here: URL
Download the correct firmware for your device and flash.
Click to expand...
Click to collapse
Thanks for your reply. I've tried many firmwares already, no luck. Here's the thing:
I'm stuck in Fastboot, it says "flashing_locked" , so I'm not allowed to flash. If you try the command "flashing unlock" it sends you to enable USB debugging and OEM unluck but I DO NOT have access to the operating system anymore.
I hope there's something I can do. Very costly paperweight I have now haha :crying:
help!
I keep trying things with no luck, it seems like I fogot my car keys inside, no spare keys, and the car is bulletproof
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-bf761ac-180305
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(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 (6)
(bootloader) serialno: ZY323366HL
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 473E091F
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 351853092729596
(bootloader) meid:
(bootloader) date: 08-22-2018
(bootloader) sku: XT1926-7
(bootloader) carrier_sku: XT1926-7
(bootloader) battid: SB18C20873
(bootloader) battery-voltage: 4150
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-2/00cb:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.2.evert.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: M660_23.40.01.85R EVERT_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gba3f1d6 (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]: Wed Feb 6 01:31:11 CST 2019
(bootloader) git:abl: MBM-3.0-uefi-bf761ac-180305
(bootloader) git:xbl: MBM-3.0-uefi-976f2e6-180305
(bootloader) git:pmic: MBM-3.0-uefi-976f2e6-180305
(bootloader) git:rpm: MBM-3.0-uefi-80b016f-180305
(bootloader) git:tz: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:hyp: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:devcfg: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:cmnlib: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:cmnlib64: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:keymaster: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:prov: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:storsec: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retla
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.297s
No luck
No love? Can't believe there's anything I can do with this. What I was thinking I know, but... still...
I've tried the method downloading the Qualcomm drivers, putting the PC in test mode, etc. but I only get the "<Waiting for device>" and nothing else happens.
Hope you can shed some light here. Thanks

After 10 Hours... I need help, please: "Invalid zip file format! error installing zip

After 10 Hours... I need help, please: "Invalid zip file format! error installing zip
Guys and gals - I just want to say in advance, thank you so much for your time and help with this, I really tried hard (over 10 hours) of referencing old xda forums and youtube videos, with nothing working so far.
Ok here it goes:
So I bought for a good price the Moto g5s Plus from ali express. Everything came fine, except one thing... it had a Chinese variant baseband flashed on the phone, which means everything worked normal except I couldn't update past 7.1.1
Baseband: M8937_37.13.03.53R Montana_Chinadsds_cust
The typical phones update to 8.1 oreo, so I want to jump on that wagon. It had been about 10 years since I've flashed or unlocked anything so I was happy to find through youtube and XDA that the process was easier. But the phone came with unlocked boot.
I put TWRP on there pretty easily and everything looked like it was going to be cake.
I was getting different errors after trying different tactics of flashing - everything from error 7, to error 1, to all kinds of errors that I've overcome... but when I'd solve one error, i'd get a different error...
I spent hours of diving through youtube / xda...
Eventually it led me to that I kept getting "cant unmount" error when trying to flash roms. I realized that tha phone isn't friendly to flashing because of something called "treble" or "trebling" - one of the developers here, liquidengineer, released a version of twrp to deal with it... but it didn't work for me.
To keep it short, after like 10 hours and nothing working... I then decided to do what was in this video:
Oreo 8.1 Stock ROM on Moto G5s Plus(English):
(notice url has a space between "youtube" and ".com")
youtube .com/watch?v=-f67lVbDqkc&t=3s
The video was nice because it was step by step. I chose to do it last because it involved using a custom script.
I followed all of the steps, the script ran. What I realized after is that this script only works if original stock roms, but I had this chinese custom rom/baseband.
In short, the script wiped everything... my partitions, files, etc...
TWRP Recovery still worked so I changed the format of the partitions to E2, then E4, that allowed me to use the phone as a drive and add the roms.
when I try to install any rom in TWRP 3.1.1-1... I now just get:
data successfully decrypted, new block device:
'/dev/block/dm-0'
Updating Partition Details....
...done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux Support is present.
MTP Enabled
Installing zip file '/sdcard/arrow-v10.0-sanders-OFFICIAL-20200329-VANILLA.zip'
Invalid zip file format!
Error installign zip file '/sdcard/arrow-v10.0-sanders-OFFICIAL-20200329-VANILLA.zip'
Updating partition details...
...done.
It doesn't matter which rom i try to install.
Factory recovery doesn't work.
I also get a Motorola error that my phone has been unlocked and cant be trusted (bad ID).
I kept this post as short as I could, and didn't include all of the different attempts I tried.... but I am now completely lost as to what to do. Please, please help! I'll paypal someone $10 for the winning answer.
-----------------------------------
Current Bootscreen:
AP Fastboot Flash Mode (Secure)
BL: BC.06(*) (sha-865eb9a-diety. 2017-07-07 15:02:25)
Bandbase: M8937_37.13.03.53R Montana_Chinadsds_cust
Product/Variant: montana XT1799-2 64 gb p3
Serial #: I have one
CPU: MSM8937
eMMC: 64 GB Samsung etc...
DRAM: 4GB SAMSUNG etc...
Console [Null]: null
Tools Mode Confid: DISABLED
BATTERY OK
flashing_unlocked
Software status: modified
Connect USB Data Cable
(as of now - using TWRP 3.1.1-1 (boots normal))
If you really have the g5s plus aka sanders, and fastboot says Montana - someone flashed a g5s aka Montana firmware, which is never a good idea.
Try flashing Sanders firmware. If that doesn't work, enjoy the paperweight
Phazmos said:
If you really have the g5s plus aka sanders, and fastboot says Montana - someone flashed a g5s aka Montana firmware, which is never a good idea.
Try flashing Sanders firmware. If that doesn't work, enjoy the paperweight
Click to expand...
Click to collapse
yes that did look odd to me. I'm not so familiar with flashing firmware, do you have any good guidance with that?
smbfission said:
yes that did look odd to me. I'm not so familiar with flashing firmware, do you have any good guidance with that?
Click to expand...
Click to collapse
What's
Code:
fastboot getvar all
give you?
Please post it here after you remove the IMEI line
Hey shadow, i feel like an idiot. It's been 10 years since I've done any of this stuff and I'm realizing there are 2 things going on...
first - even though I bought a g5s Plus (also called sanders), that's not what I got. I unknowingly got a g5s (without the plus). Still, it should have installed probably anyway... regardless of whether it's a plus or not. So not sure why I get the errors - will that happen if the phone distro's don't match?
Finally, the moto g5s's are not all the same, because they each carry their own country. And in my case, I have the xt1799-2 - which is the chinese ZUI variant (customized lenovo version), which makes it more complex.
One guy sent me this: https://forum.xda-developers.com/moto-g5s/how-to/guide-moto-g5sxt179x-stock-rom-t3839003/amp/
however... the problem is because he uses the Chinese language firmware, it still seems he's stuck in 7.1.1 which won't even allow me to use custom roms because most of them rely on the 8.1 oreo firmware. Do you guys see holes in his approach?
Although to answer your question, do you want me just to run that function?
sd_shadow said:
What's
Code:
fastboot getvar all
give you?
Please post it here after you remove the IMEI line
Click to expand...
Click to collapse
smbfission said:
Hey shadow, i feel like an idiot. It's been 10 years since I've done any of this stuff and I'm realizing there are 2 things going on...
first - even though I bought a g5s Plus (also called sanders), that's not what I got. I unknowingly got a g5s (without the plus). Still, it should have installed probably anyway... regardless of whether it's a plus or not. So not sure why I get the errors - will that happen if the phone distro's don't match?
Finally, the moto g5s's are not all the same, because they each carry their own country. And in my case, I have the xt1799-2 - which is the chinese ZUI variant (customized lenovo version), which makes it more complex.
One guy sent me this: https://forum.xda-developers.com/moto-g5s/how-to/guide-moto-g5sxt179x-stock-rom-t3839003/amp/
however... the problem is because he uses the Chinese language firmware, it still seems he's stuck in 7.1.1 which won't even allow me to use custom roms because most of them rely on the 8.1 oreo firmware. Do you guys see holes in his approach?
Although to answer your question, do you want me just to run that function?
Click to expand...
Click to collapse
The getvar all give a lot of info about what is going on with the device.
So yes please.
Thanks so much in advance:
Just one note - even though it says I have a rom, i cant boot into it because as mentioned, i ran a script for g5s+ and it more or less corrupted it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.06(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322WHXP7
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: 758A323800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) I removed this as mentioned
(bootloader) meid:
(bootloader) date: 09-06-2018
(bootloader) sku: XT1799-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 18 5: 1:50 UTC 1971"
(bootloader) ro.build.fingerprint[0]: motorola/montana_retcn_n/montana_n
(bootloader) ro.build.fingerprint[1]: :7.1.1/NZS26.86-128/112:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.112.montana_re
(bootloader) ro.build.version.full[1]: tcn.retcn.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8937_37.13.03.53R MONTANA_CHINADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g647ff94-0000
(bootloader) kernel.version[1]: 7-g13fa5e2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Wed Apr
(bootloader) kernel.version[3]: 11 23:05:29 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.06-0-g518a6f1
(bootloader) rpm.git: git=aa33522-dirty
(bootloader) tz.git: git=1fe3cc8-dirty
(bootloader) devcfg.git: git=1fe3cc8-dirty
(bootloader) keymaster.git: git=1fe3cc8-dirty
(bootloader) cmnlib.git: git=1fe3cc8-dirty
(bootloader) cmnlib64.git: git=1fe3cc8-dirty
(bootloader) prov.git: git=1fe3cc8-dirty
(bootloader) aboot.git: git=MBM-NG-VBC.06-0-g865eb9a-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcn
all: listed above
finished. total time: 1.195s
sd_shadow said:
The getvar all give a lot of info about what is going on with the device.
So yes please.
Click to expand...
Click to collapse
smbfission said:
Thanks so much in advance:
Just one note - even though it says I have a rom, i cant boot into it because as mentioned, i ran a script for g5s+ and it more or less corrupted it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.06(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322WHXP7
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: 758A323800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) I removed this as mentioned
(bootloader) meid:
(bootloader) date: 09-06-2018
(bootloader) sku: XT1799-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 18 5: 1:50 UTC 1971"
(bootloader) ro.build.fingerprint[0]: motorola/montana_retcn_n/montana_n
(bootloader) ro.build.fingerprint[1]: :7.1.1/NZS26.86-128/112:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.112.montana_re
(bootloader) ro.build.version.full[1]: tcn.retcn.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8937_37.13.03.53R MONTANA_CHINADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g647ff94-0000
(bootloader) kernel.version[1]: 7-g13fa5e2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Wed Apr
(bootloader) kernel.version[3]: 11 23:05:29 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.06-0-g518a6f1
(bootloader) rpm.git: git=aa33522-dirty
(bootloader) tz.git: git=1fe3cc8-dirty
(bootloader) devcfg.git: git=1fe3cc8-dirty
(bootloader) keymaster.git: git=1fe3cc8-dirty
(bootloader) cmnlib.git: git=1fe3cc8-dirty
(bootloader) cmnlib64.git: git=1fe3cc8-dirty
(bootloader) prov.git: git=1fe3cc8-dirty
(bootloader) aboot.git: git=MBM-NG-VBC.06-0-g865eb9a-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcn
all: listed above
finished. total time: 1.195s
Click to expand...
Click to collapse
So, the correct Firmware for your device is Montana/RetCN/XT1799-2
https://mirrors.lolinet.com/firmware/moto/montana_retcn/official/RETCN/
which looks like has only been updated to 7.1.1 blur 26.68-117
You could try Retail software channel
https://mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/
But I can't tell which model that is for...
RetEU is XT1793/XT1794
RetGB is XT1794
Doesn't look like there is a RetUS which is preferred if you live in the USA.
and I'm not seeing if there are any hardware differences between them.
I guess I would flash RetCN just to get it back to stock and working again.
If that goes good, try the Retail.
I've posted some general flashing instructions in
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
sd_shadow said:
So, the correct Firmware for your device is Montana/RetCN/XT1799-2
https://mirrors.lolinet.com/firmware/moto/montana_retcn/official/RETCN/
which looks like has only been updated to 7.1.1 blur 26.68-117
You could try Retail software channel
https://mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/
But I can't tell which model that is for...
RetEU is XT1793/XT1794
RetGB is XT1794
Doesn't look like there is a RetUS which is preferred if you live in the USA.
and I'm not seeing if there are any hardware differences between them.
I guess I would flash RetCN just to get it back to stock and working again.
If that goes good, try the Retail.
I've posted some general flashing instructions in
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
Quick question - it seems that the Russians have a lot more support and roms for xt1799-2, because probably they buy from aliexpress. What I don't get is if you take this thread, https://4pda.ru/forum/index.php?showtopic=886009&st=260#entry76570414 (translate with google translate chrome extension)
people are installing custom ROM For XT1799-2
crDroid v4.7.2 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=89050911
crDroid v5.11 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=92946311
Do they first install the stock 7.1.1 firmware? and then the ROM, even though 4.7.2 is Android 8.1, and crDroid 5.11 is Android 9.0?
Does the firmware version need to match the ROM version?
Also, if i want to avoid risking to mess up the bootloader, can i just leave out the following:
fastboot of flash partition gpt.bin
fastboot of flash the bootloader bootloader.img
smbfission said:
Quick question - it seems that the Russians have a lot more support and roms for xt1799-2, because probably they buy from aliexpress. What I don't get is if you take this thread, https://4pda.ru/forum/index.php?showtopic=886009&st=260#entry76570414 (translate with google translate chrome extension)
people are installing custom ROM For XT1799-2
crDroid v4.7.2 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=89050911
crDroid v5.11 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=92946311
Do they first install the stock 7.1.1 firmware? and then the ROM, even though 4.7.2 is Android 8.1, and crDroid 5.11 is Android 9.0?
Does the firmware version need to match the ROM version?
Also, if i want to avoid risking to mess up the bootloader, can i just leave out the following:
fastboot of flash partition gpt.bin
fastboot of flash the bootloader bootloader.img
Click to expand...
Click to collapse
I believe they are on stock 7.1.1, and installing the updated custom rom.
Likely there is not much of 7.1.1 left other than the bootloader.
Sent from my ali using XDA Labs

Moto G2 XT1072 can't boot

Hi all,
I had a XT1072 with Android 6 and wanted to go back to 5 due to problems with GPS.
I unlocked the boot loader, flashed stock ROM with Android 6 and all was fine.
I next tried to flash stock ROM with Android 5 and was stuck in fast boot with errors like "invalid system image signature" or similar.
Next I messed around with TWRP, stock again, lock, unlock... a mess.
Now it's stuck in fastboot with status "LOCKED, status code 2" (0 is LOCKED, 3 UNLOCKED, 2 what is it?)
I tried flashing stock ROM both 5 and 6 in different versions:
RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETESALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
Motorola_Moto_G2_XT1072_MPB24.65-34_CID12_6.0
But all fail with "failed validation";
Unlock fails, but I cannot boot in Android to change mentioned option:
Code:
mfastboot-v2> .\mfastboot oem unlock XSVDURWNGOWYDFMGU5ZT
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.057s
RSD Lite to flash stock ROM doesn't see my device.
Rescue and Smart Assistant cannot proceed due to "missing version-baseband:" (see empty var listed below).
Code:
mfastboot-v2> .\mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4821
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2272TX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: C96B590915000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 2
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from mot-charger boot mode
(bootloader) imei: 353310061467870
(bootloader) meid:
(bootloader) date: 04-28-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Sep 16 3: 2:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.thea_reteu.
(bootloader) ro.build.version.full[1]: reteuall.en.EU
(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:
(bootloader) kernel.version[0]: Linux version 3.4.42-g495dfd8 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Sat Sep 10 01:48:29 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V48.21-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.21-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.21-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.21-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.21-0-gd8d8d9e
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C2272TX
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.105s
Do you have any suggestions to restore it?
Let me know if I can give you more information.
Thanks
enricocava said:
Hi all,
I had a XT1072 with Android 6 and wanted to go back to 5 due to problems with GPS.
I unlocked the boot loader, flashed stock ROM with Android 6 and all was fine.
I next tried to flash stock ROM with Android 5 and was stuck in fast boot with errors like "invalid system image signature" or similar.
Next I messed around with TWRP, stock again, lock, unlock... a mess.
Now it's stuck in fastboot with status "LOCKED, status code 2" (0 is LOCKED, 3 UNLOCKED, 2 what is it?)
Click to expand...
Click to collapse
Sometimes the bootloader will relock, when using a custom recovery is used.
I'm not sure why usually when trying to install a rom.
It's very common, but it happens on many Moto devices.
enricocava said:
I tried flashing stock ROM both 5 and 6 in different versions:
RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETESALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
Motorola_Moto_G2_XT1072_MPB24.65-34_CID12_6.0
Click to expand...
Click to collapse
That will have made it worse.
enricocava said:
But all fail with "failed validation";
Unlocking fails with "Please allow OEM unlock from developer options", but Android is not booting so I cannot change it.
RSD Lite to flash stock ROM doesn't see my device.
Click to expand...
Click to collapse
RSD Lite doesn't work with Windows 9/10/11
Use XP/7
enricocava said:
Rescue and Smart Assistant cannot proceed due to "missing base version" (string is not correct, I'll chek it later).
Do you have any suggestions to restore it?
Let me know if I can give you more information.
Thanks
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
[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
Thank you for your quick reply.
sd_shadow said:
RSD Lite doesn't work with Windows 9/10/11
Use XP/7
Click to expand...
Click to collapse
Colud it work on a Win7 on a Virtual machine or does it need direct access to USB ports? At the moment I have not an old Windows available.
sd_shadow said:
What does getvar all say?
Click to expand...
Click to collapse
I updated the original post.
sd_shadow said:
[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 missed this post, I'll take a look.
enricocava said:
Hi all,
I had a XT1072 with Android 6 and wanted to go back to 5 due to problems with GPS.
I unlocked the boot loader, flashed stock ROM with Android 6 and all was fine.
I next tried to flash stock ROM with Android 5 and was stuck in fast boot with errors like "invalid system image signature" or similar.
Next I messed around with TWRP, stock again, lock, unlock... a mess.
Now it's stuck in fastboot with status "LOCKED, status code 2" (0 is LOCKED, 3 UNLOCKED, 2 what is it?)
I tried flashing stock ROM both 5 and 6 in different versions:
RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETESALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
Motorola_Moto_G2_XT1072_MPB24.65-34_CID12_6.0
But all fail with "failed validation";
Unlock fails, but I cannot boot in Android to change mentioned option:
Code:
mfastboot-v2> .\mfastboot oem unlock XSVDURWNGOWYDFMGU5ZT
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.057s
RSD Lite to flash stock ROM doesn't see my device.
Rescue and Smart Assistant cannot proceed due to "missing version-baseband:" (see empty var listed below).
Code:
mfastboot-v2> .\mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4821
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2272TX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: C96B590915000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 2
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from mot-charger boot mode
(bootloader) imei: 353310061467870
(bootloader) meid:
(bootloader) date: 04-28-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Sep 16 3: 2:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.thea_reteu.
(bootloader) ro.build.version.full[1]: reteuall.en.EU
(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:
(bootloader) kernel.version[0]: Linux version 3.4.42-g495dfd8 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Sat Sep 10 01:48:29 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V48.21-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.21-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.21-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.21-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.21-0-gd8d8d9e
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C2272TX
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.105s
Do you have any suggestions to restore it?
Let me know if I can give you more information.
Thanks
Click to expand...
Click to collapse
Code:
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
This should be the correct firmware
https://mirrors-obs-2.lolinet.com/firmware/motorola/2015/thea/official/RETEU/
XT1072_THEA_RETEU_6.0_MPBS24.65-34-5_cid7_subsidy-DEFAULT_CFC.xml.zip
Try flashing
Code:
fastboot flash partition gpt.bin
fastboot reboot bootloader
Then flash the firmware using the flash_file.xml as reference.
sd_shadow said:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
This should be the correct firmware
https://mirrors-obs-2.lolinet.com/firmware/motorola/2015/thea/official/RETEU/
XT1072_THEA_RETEU_6.0_MPBS24.65-34-5_cid7_subsidy-DEFAULT_CFC.xml.zip
Try flashing
Code:
fastboot flash partition gpt.bin
fastboot reboot bootloader
Then flash the firmware using the flash_file.xml as reference.
Click to expand...
Click to collapse
Thank you, it worked! So the problem was the wrong fw version and messing up gpt with random commands, right?
For a downgrade I can follow this one, right? https://forum.xda-developers.com/t/guide-flashing-motorola-firmware.4042039/post-84863341
enricocava said:
Thank you, it worked! So the problem was the wrong fw version and messing up gpt with random commands, right?
Click to expand...
Click to collapse
I believe so
enricocava said:
For a downgrade I can follow this one, right? https://forum.xda-developers.com/t/guide-flashing-motorola-firmware.4042039/post-84863341
Click to expand...
Click to collapse
Do not downgrade unless the bootloader says unlocked again.
If the bootloader is reported as unlocked again,
sure you should be able to downgrade the firmware.

Hard Bricked (EDL) moto g9 play XT2083-1

Help needed
My device is on EDL mode ( showing on device manager as Qualcomm HS-USB QDLoader 9008).
I tried every single blankfash file from lolinet and my device not booted.
Mine is the brazillian version (XT2083-1_GUAMP_RETBR).
Someone have the correct file for Blankflashing my device or other solution for my problem?
Thanks in advance.
Hello friend, I created a Blankflash based on the latest version of android 11 (RPX31.Q2-58-17-7), it worked for me, if you want to try it do it at your own risk, I am not responsible for any possible problems let it happen.
RMS100 said:
Hello friend, I created a Blankflash based on the latest version of android 11 (RPX31.Q2-58-17-7), it worked for me, if you want to try it do it at your own risk, I am not responsible for any possible problems let it happen.
Click to expand...
Click to collapse
Worked fine for me, thank you.
my phone also returned to image, what did you do after that?
vtrxz said:
my phone also returned to image, what did you do after that?
Click to expand...
Click to collapse
You can use this tool from motorola to flash the latest Stock Rom on your device: https://www.motorola.com/us/rescue-and-smart-assistant/p
Thank you very much, my phone is working again thanks to you
RMS100 said:
Olá amigo, criei um Blankflash baseado na última versão do android 11 (RPX31.Q2-58-17-7), funcionou para mim, se você quiser experimentar faça por sua conta e risco, não me responsabilizo por quaisquer problemas possíveis deixe acontecer.
Click to expand...
Click to collapse
God bless you my friend, save me a lot!!!
Hello, I had the same problem and managed to get out of EDL mode, but when trying to install the stock rom via fastboot, an error occurred and, in the failed attempt to solve it, I ended up blocking the bootloader. Now I have my device bricked and the bootloader is locked.
I've already used Rescue and Smart Assistant and it can't finish the process. I can't flash any roms through adb either. It really is a misfortune.
Below is the information about my device:
C:\Users\whoami\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-guamp_retail-252ee94a78-220503
(bootloader) product: guamp
(bootloader) board: guamp
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DP6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: 0073117509
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: B74625DD
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804464640
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 352234676210270
(bootloader) imei2: 352234676210288
(bootloader) meid:
(bootloader) date: 04-30-2021
(bootloader) sku: XT2083-1
(bootloader) carrier_sku: XT2083-1
(bootloader) battid: SB18C45530
(bootloader) battery-voltage: 3904
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/guamp_retail/guamp:11/RPX
(bootloader) ro.build.fingerprint[1]: 31.Q2-58-17-7/c9ebb:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-02200-KAMORTA.0
(bootloader) version-baseband: HA10_32.40.02.106R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[4]: pr 29 11:24:11 CDT 2022
(bootloader) git:xbl: MBM-3.0-guamp_retail-0ed29cb2f-220503
(bootloader) git:xbl_config: MBM-3.0-guamp_retail-0ed29cb2f-220503
(bootloader) git:abl: MBM-3.0-guamp_retail-252ee94a78-220503
(bootloader) git:rpm: MBM-3.0-guamp_retail-834e250d-220503
(bootloader) git:tz: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:hyp: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:devcfg: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:keymaster: MBM-3.0-guamp_retail-4b088521-220503
(bootloader) git:storsec: MBM-3.0-guamp_retail-4b088521-220503
(bootloader) git:uefisecapp: MBM-3.0-guamp_retail-4b088521-220503
(bootloader) gitrov: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:qupfw: MBM-3.0-guamp_retail-2c412ce-220503
(bootloader) frp-state: protected (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D19213
(bootloader) primary-display: hlt_ili9882h_video_display
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.125s
friend, I have the same problem, the motorola updated and the version of the blankflash that I need is the version RPXS31.Q2-58-17-7-2 I looked in several places on the internet and it really doesn't have it. help!
L1p3Droid_BR said:
friend, I have the same problem, the motorola updated and the version of the blankflash that I need is the version RPXS31.Q2-58-17-7-2 I looked in several places on the internet and it really doesn't have it. help!
Click to expand...
Click to collapse
Did you try the blankflash that was made available here? maybe it still works as the latest Motorola update was just a security patch.
RMS100 said:
Did you try the blankflash that was made available here? maybe it still works as the latest Motorola update was just a security patch.
Click to expand...
Click to collapse
yes, I tried but without success.
RMS100 said:
Did you try the blankflash that was made available here? maybe it still works as the latest Motorola update was just a security patch.
Click to expand...
Click to collapse
follows the photo, but it does not restart to fastboot. it is version xt2083-3 retbr
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
L1p3Droid_BR said:
follows the photo, but it does not restart to fastboot. it is version xt2083-3 retb
Click to expand...
Click to collapse
L1p3Droid_BR said:
follows the photo, but it does not restart to fastboot. it is version xt2083-3 retbrView attachment 5701121
Click to expand...
Click to collapse
Ok, try this, download LSMA from motorola and try to run the fastboot commands with the device connected to the PC with the program already open. if the device is recognized, download the stock and install using the program.
RMS100 said:
Ok, try this, download LSMA from motorola and try to run the fastboot commands with the device connected to the PC with the program already open. if the device is recognized, download the stock and install using the program.
Click to expand...
Click to collapse
the device does not turn on. even the cmd command saying that it was completed for fastboot, but it is false, it does not show any signal, it just exits edl mode only and unresponsive and does not recognize on the computer even with drivers and platform tools configured on the computer. It's a brick, it only enters edl at the moment, I believe only with the blankflash of the current version.
RMS100 said:
Ok, try this, download LSMA from motorola and try to run the fastboot commands with the device connected to the PC with the program already open. if the device is recognized, download the stock and install using the program.
Click to expand...
Click to collapse
Worse than I've done it using LMSA, I left it in the background and it's still not recognized.
L1p3Droid_BR said:
Worse than I've done it using LMSA, I left it in the background and it's still not recognized.
Click to expand...
Click to collapse
Hello friend, I didn't find a specific firmware for your model (XT2083-3), apparently the only difference between this model and the XT2083-1 is the NFC, so I made this blankflash based on the latest firmware of the model XT2083-1. If you want to try, do it at your own risk, I am not responsible for any problems.
RMS100 said:
Hello friend, I didn't find a specific firmware for your model (XT2083-3), apparently the only difference between this model and the XT2083-1 is the NFC, so I made this blankflash based on the latest firmware of the model XT2083-1. If you want to try, do it at your own risk, I am not responsible for any problems.
Click to expand...
Click to collapse
I tried, I didn't succeed. I tried, without success. this phone's software is hosted on lolinet. can you flash this software? Follow the link https://mirrors.lolinet.com/firmware/motorola/guamp/official/RETBR/
L1p3Droid_BR said:
Eu tentei, não tive sucesso. Eu tentei, sem sucesso. o software deste telefone está hospedado no lolinet. você pode mostrar este software? Siga o link https://mirrors.lolinet.com/firmware/motorola/guamp/official/RETBR/
Click to expand...
Click to collapse
Hi, I used exactly the firmware available on lolinet, I think unfortunately I can't do anything else for you.
RMS100 said:
Hi, I used exactly the firmware available on lolinet, I think unfortunately I can't do anything else for you.
Click to expand...
Click to collapse
Thank you for making yourself available to help. It went into Hard brick after deleting the vendor by passing a gsi. At least the blankflash created can help another forum member.
hello someones knows where are the edl points in moto g9 play? i putted in contacts a lot of places and i cant know the place

Categories

Resources