Develop Bugs

XT1710-09 Bricked

Hello guys,
I need a help. I was trying to update my moto using this thread: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153
Everything seemed to be fine until the restart. Phones starts imidately in Fastboot mode with ERROR: Failed to pass validation, backup to fastboot. Now I can't do anything. I've tried to flash other roms, using also that thread: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479 but during the installation it gives many error about downgrading to older security version. Any Ideas? I was trying to find blanckflash but qboot doesn't see the phone. What can I do with that?
with command getvar all I get this. Maybe it will be helpfull.
HTML:
D:\moto recover\>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.CD
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2249PJMN
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: EDCCE8F000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 351888080876090
(bootloader) meid:
(bootloader) date: 07-24-2017
(bootloader) sku: XT1710-09
(bootloader) carrier_sku:
(bootloader) battid: SNN5985A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jan 25 4:33:24 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/albus_playpl/albus:7.1.1/
(bootloader) ro.build.fingerprint[1]: NPSS26.118-33-9/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.301.12.albus_play
(bootloader) ro.build.version.full[1]: pl.playpl.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953P_23.33.07.34R ALBUS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g2371d89-0010
(bootloader) kernel.version[1]: 2-g249f1d8 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Sat Feb 3 11:22:52 CST 201
(bootloader) kernel.version[4]: 8
(bootloader) sbl1.git: git=MBM-NG-VC0.CD-0-g4650d8f
(bootloader) rpm.git: git=MBM-NG-VC1.82-0-gbd19194
(bootloader) tz.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) devcfg.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) keymaster.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) prov.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.CD-0-g361b83a
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.047s

Do you unlock bootloader before?

Mark2014 said:
Do you unlock bootloader before?
Click to expand...
Click to collapse
Actually not... I assumed it was unlocked...

rembick said:
Actually not... I assumed it was unlocked...
Click to expand...
Click to collapse
You flash rom without unlock bootloader !!!
sorry, I cant help.

Mark2014 said:
You flash rom without unlock bootloader !!!
sorry, I cant help.
Click to expand...
Click to collapse
Thanks anyway, cheers.

How did you flash the Oreo stock ROM in the first place, did you use the script or did you manually flash the commands? Do you still have the flashing log to upload (i.e. the output from the ADB terminal)?
If that's your getvar output after the flash, then it looks like the Oreo update did not work (you're still on 7.1.1). Is your device on the Play.pl carrier btw? It looks like you're receiving some Play.pl specific firmware?
Code:
Blur_Version.26.301.12.albus_playpl.playpl.en.US
Your bootloader is locked, which is why it's falling back to fastboot mode
Code:
(bootloader) securestate: oem_locked
- OEM_locked represents a locked bootloader.
EDIT - Having downloaded and looked at the albus Oreo update, it looks like your bootloader got updated to the Oreo bootloader (version C0.CD), but the rest of your device was not updated. Hence, your device bootloader performed the integrity checks expecting Oreo firmware and failed to boot as you still have 7.1.1 firmware on your device.
Are you able to re-flash the Oreo stock firmware, and if so, can you provide us with a flash log please? If another flash does not work in getting your device working, you may have to consult your carrier or retailer for assistance.
Here's the info for the Oreo stock ROM:
Code:
BUILD REQUEST INFO:
SW Version: albus-user 8.0.0 OPS27.76-12-25 26 release-keysM8953P_41.50.07.63R
MBM Version: C0.CD
Modem Version: M8953P_41.50.07.63R
FSG Version: FSG-8953-08.120
Build Fingerprint: motorola/albus/albus:8.0.0/OPS27.76-12-25/26:user/release-keys
CQATest App Version: 6.0.3
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 27.21.26.albus.retail.en.US
Model Number: Moto Z2 Play
Android Version: 8.0.0
Baseband Version: M8953P_41.50.07.63R
Build Id: OPS27.76-12-25
SW Display Build ID: OPS27.76-12-25
Build Date: Wed Apr 4 07:17:22 CDT 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.27.21.26.albus.retail.en.US
Version when read from CPV: albus-user 8.0.0 OPS27.76-12-25 26 release-keys
AB Update Enabled: False
Full Treble Enabled: False

Hi. I have a same version - 09. Just bought on days and manually updated to Oreo.
Just use easily this commands set from post you mentioned:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear

Thanks for reply guys, I was away couple of days. I will try your solutions today and give feedback.
EDIT:
Hi. I have a same version - 09. Just bought on days and manually updated to Oreo.
Just use easily this commands set from post you mentioned:
Click to expand...
Click to collapse
Thank you man! You've saved me! your solution works and also I got rid of carrier software from my phone. Thank you one more time.

rembick said:
Thanks for reply guys, I was away couple of days. I will try your solutions today and give feedback.
EDIT:
Thank you man! You've saved me! your solution works and also I got rid of carrier software from my phone. Thank you one more time.
Click to expand...
Click to collapse
May I know If you flash through fastboot with locked bootloader or not ?
Thanks.

kuro_neko said:
May I know If you flash through fastboot with locked bootloader or not ?
Thanks.
Click to expand...
Click to collapse
I didn't unlock bootloader. Just flashed through Fastboot using the commands one by one not using any .bat file.

You problem (bootloader) cid: 0x0032

Hey, I also got a problem with XT1710-09, but it's a little bit different one.
I rooted it with Magisk and wanted to install an OTA, so I unrooted it.
Then all my problems started to come to light.
Somehow I managed to modify content of /system partition, so OTA installation was unsuccessful.
Then I remembered that before rooting I made a backup with TWRP, so I tried to restore only system partition from that backup.
Unfortunately, my phone couldn't boot. Then I made a decision to flash just system partition from some other image (well, this one in particular: ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
Ok, my phone started working again, but then I noticed that no OTA were available for my phone.
Today I investigated a bit, found OTAs and tried to sideload them.
This time error was: build fingerprint error.
Well, yeah, at first I tried to install http://erfanoabdi.000webhostapp.com...on.26.241.16.albus.retail.en.US&carrier=reteu which was meant for "albus", but my phone is branded for Play.
Then I tried to install http://erfanoabdi.000webhostapp.com...51.29.albus_playpl.playpl.en.US&carrier=reteu. This time I got the version for "albus_playpl", but build version was not right, due to flashing system partition which I described above.
And here is my question: what I should do now?
I really don't want to lose any data, nor do I want to install my apps all again.
Is there any solution for me to get it right?

zaq21wsx said:
Then I made a decision to flash just system partition from some other image (well, this one in particular: ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
Click to expand...
Click to collapse
NPSS26.118-19-14 is "November 2017". Did you have that version before? If not, restoring only the System partition will break the OTA upgrade script because it verifies Boot and Oem partitions as well.
My suggestion is to flash the following partitions from the stock image: gpt, bootloader, logo, boot, oem, system
With that the data remains intact then you can try to check for OTA again.

wsemi said:
NPSS26.118-19-14 is "November 2017". Did you have that version before? If not, restoring only the System partition will break the OTA upgrade script because it verifies Boot and Oem partitions as well.
My suggestion is to flash the following partitions from the stock image: gpt, bootloader, logo, boot, oem, system
With that the data remains intact then you can try to check for OTA again.
Click to expand...
Click to collapse
But now I don't really know what version I had before, because of that branded software. It's nowhere to be found on the internet...
Is changing ro.product.name in build.prop any solution for "albus" from "albus_playpl"? Or how does it change when I'll be flashing another image?

zaq21wsx said:
But now I don't really know what version I had before, because of that branded software. It's nowhere to be found on the internet...
Is changing ro.product.name in build.prop any solution for "albus" from "albus_playpl"? Or how does it change when I'll be flashing another image?
Click to expand...
Click to collapse
Don't change build.prop. Product name should not change, albus_playpl version is probably for different device.
Try to flash ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip without "erase userdata".

wsemi said:
Don't change build.prop. Product name should not change, albus_playpl version is probably for different device.
Try to flash ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip without "erase userdata".
Click to expand...
Click to collapse
But now I have "albus_playpl" with system image from NPSS26.118-19-14.
Btw what is the difference between ALBUS_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip? And will it be good for my XT1710-09?

zaq21wsx said:
But now I have "albus_playpl" with system image from NPSS26.118-19-14.
Btw what is the difference between ALBUS_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip? And will it be good for my XT1710-09?
Click to expand...
Click to collapse
Ok, I get it know. At the first reading I didn't catch that "Play" is also the name of your mobile carrier. They sold the device with "albus_playpl" firmware. Probably they just put some bloatware or limitation on top of the retail version.
Currently your partitions are inconsistent and seems there is no way to get a full "playpl" firmware. So to make the partitions consistent again you can flash a full retail (carrier independent) firmware. I believe if you do that (as previously described) you will get the OTA updates as well.

wsemi said:
Ok, I get it know. At the first reading I didn't catch that "Play" is also the name of your mobile carrier. They sold the device with "albus_playpl" firmware. Probably they just put some bloatware or limitation on top of the retail version.
Currently your partitions are inconsistent and seems there is no way to get a full "playpl" firmware. So to make the partitions consistent again you can flash a full retail (carrier independent) firmware. I believe if you do that (as previously described) you will get the OTA updates as well.
Click to expand...
Click to collapse
Yeah, that's a sad coincidence in my case... Well, I'll come back to it, when I have more free time to have fun with flashing new firmware.
You only suggest not to flash data partition, but which one is it?
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata # is it this one? should I just omit it?
fastboot erase DDR
fastboot oem fb_mode_clear

zaq21wsx said:
Code:
fastboot erase userdata # is it this one? should I just omit it?
Click to expand...
Click to collapse
Exactly. Omitting that line should keep the data and internal storage. But to be sure you can make backup to a usb stick.

Moto Z2 Play
My Moto Z2 Play is bricked after system update November 2017.
Bootloader was unlocked.
Now phone is showing on PC as Qualcomm HS-USB QDLoader 9008.
Please help

Help 0 imei no wifi no cellular signal

I have the xt1789-04 I updated it to android 9.0 without flashing the modems everything worked fine then did flash all to Oreo and the fhlashed pixel experience ROM witch got me into bootloop so I flash Oreo again and now I have now WiFi no data no imei and I tried flashing twrp but it won’t let me keeps on appearing an error message

I had similar issue and I tried following file and it helped me. below code will erase everything on your phone so proceed with caution.
if you are on fastboot mode, try flashing stock oreo with bothslotflashall.bat file(below code). If you dont have mfastboot, please edit below code with "fastboot" command.
fastboot erase all
mfastboot oem fb_mode_set
mfastboot getvar max-sparse-size
mfastboot flash partition gpt.bin
mfastboot flash bootloader_a bootloader.img
mfastboot flash bootloader_b bootloader.img
mfastboot flash modem_a NON-HLOS.bin
mfastboot flash fsg_a fsg.mbn
mfastboot flash modem_b NON-HLOS.bin
mfastboot flash fsg_b fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth_a BTFM.bin
mfastboot flash dsp_a adspso.bin
mfastboot flash logo_a logo.bin
mfastboot flash boot_a boot.img
mfastboot flash system_a system.img_sparsechunk.0
mfastboot flash system_a system.img_sparsechunk.1
mfastboot flash system_a system.img_sparsechunk.2
mfastboot flash system_a system.img_sparsechunk.3
mfastboot flash system_a system.img_sparsechunk.4
mfastboot flash system_a system.img_sparsechunk.5
mfastboot flash oem_a oem.img
mfastboot flash bluetooth_b BTFM.bin
mfastboot flash dsp_b adspso.bin
mfastboot flash logo_b logo.bin
mfastboot flash boot_b boot.img
mfastboot flash system_b system.img_sparsechunk.0
mfastboot flash system_b system.img_sparsechunk.1
mfastboot flash system_b system.img_sparsechunk.2
mfastboot flash system_b system.img_sparsechunk.3
mfastboot flash system_b system.img_sparsechunk.4
mfastboot flash system_b system.img_sparsechunk.5
mfastboot flash oem_b oem.img
mfastboot erase carrier
mfastboot erase ddr
mfastboot oem fb_mode_clear
mfastboot -w
mfastboot --set-active=other
mfastboot reboot-bootloader
Click to expand...
Click to collapse

Will try it when I get home and will let you know for now thank you

latadswapnil said:
I had similar issue and I tried following file and it helped me. below code will erase everything on your phone so proceed with caution.
if you are on fastboot mode, try flashing stock oreo with bothslotflashall.bat file(below code). If you dont have mfastboot, please edit below code with "fastboot" command.
Click to expand...
Click to collapse
Any risk to run "fastboot erase all"
My baseband "Not Found".
Sent from my LG-LS997 using Tapatalk

cgigate said:
Any risk to run "fastboot erase all"
My baseband "Not Found".
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
erase all will erase all the partitions, I have done this on my XT1789-04 several times and never faced any issue.
But be sure that you have a stock rom to flash.

latadswapnil said:
erase all will erase all the partitions, I have done this on my XT1789-04 several times and never faced any issue.
But be sure that you have a stock rom to flash.
Click to expand...
Click to collapse
Actually. the "erase all" does very little things, I wish it can erase the modem_a and modem_b partitions.
>fastboot erase all
erasing 'all'...
(bootloader) erasing ddr ...
(bootloader) erasing carrier ...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing fsc ...
(bootloader) erasing userdata ...
(bootloader) erasing fsg_a ...
(bootloader) erasing fsg_b ...
OKAY [ 0.829s]
finished. total time: 0.830s

cgigate said:
Actually. the "erase all" does very little things, I wish it can erase the modem_a and modem_b partitions.
>fastboot erase all
erasing 'all'...
(bootloader) erasing ddr ...
(bootloader) erasing carrier ...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing fsc ...
(bootloader) erasing userdata ...
(bootloader) erasing fsg_a ...
(bootloader) erasing fsg_b ...
OKAY [ 0.829s]
finished. total time: 0.830s
Click to expand...
Click to collapse
Yeah it doesn't, I dont understand why cant we able to format these system partitions, I thought of blankflashing older bootloader and install older stock rom but my phone doesnt go in EDL mode.

latadswapnil said:
Yeah it doesn't, I dont understand why cant we able to format these system partitions, I thought of blankflashing older bootloader and install older stock rom but my phone doesnt go in EDL mode.
Click to expand...
Click to collapse
Actually, it is very easy to get in EDL mode.

cgigate said:
Actually, it is very easy to get in EDL mode.
Click to expand...
Click to collapse
I tried all the methods available online such as "adl reboot edl" or from twrp nothing works. Phone just reboots normally , once or twice screen went blank but then again system didnt detect the phone and phone rebooted again normally in 30 seconds automatically.
I tried USB 2.0, 3.0, USB C but nothing is working.

latadswapnil said:
I tried all the methods available online such as "adl reboot edl" or from twrp nothing works. Phone just reboots normally , once or twice screen went blank but then again system didnt detect the phone and phone rebooted again normally in 30 seconds automatically.
I tried USB 2.0, 3.0, USB C but nothing is working.
Click to expand...
Click to collapse
"adb reboot edl" works well to get in EDL mode from TWRP.
there is a timing issue
All you needs is to run "flashblanl.bat" in another CMD windows, then immediately issue ""adb reboot edl" command in a CMD windows under twrp,
but my blankflashing can flash, you can see the progress and logs, but it eventually failed, I may need to make another blank flash single image file

gave it a try and it didnt let me flash this is what appeared
quote: C:\Users\gustavo\Downloads\TMO Moto Z2 Force 27.1.5 flashall\TMO Moto Z2 Force 27.1.5 flashall>fastboot erase all
(bootloader) partition-ty: not found
erasing 'all'...
(bootloader) Invalid partition name allrtition-ty
FAILED (remote failure)
finished. total time: 0.023s

i was able to flash the comands but still imei unavailable and no cellular signal and no wifi

Moto G8 play boot loop

Hi
my moto g8 (xt2015-2) went into boot looping after I tried to root using this tutorial:
https://www.getdroidtips.com/root-moto-g8-play/
I have already made several attempts to install several roms stocks, like these:
https://www.stockrom.net/2020/04/xt2015-2-pie-retail-latam-pmd29-70-81.html
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETAIL/
I used adb flash tools as the method in flashfile.xml inside the rom.
my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-dd9cedf-190906
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZF522784QB
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 32AA9F6547C0BDE1000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 11-13-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C55376
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 2 3:10:57 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMDS29.70-
(bootloader) ro.build.fingerprint[1]: 70-2/ac5451:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.2.lima_32.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V16.03.01.88R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 55) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Thu Dec 26 1
(bootloader) kernel.version[3]: 0:20:37 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C70602
all: listed above
finished. total time: 0.007s
Click to expand...
Click to collapse

adrianosk8 said:
Hi
my moto g8 (xt2015-2) went into boot looping after I tried to root using this tutorial:
https://www.getdroidtips.com/root-moto-g8-play/
I have already made several attempts to install several roms stocks, like these:
https://www.stockrom.net/2020/04/xt2015-2-pie-retail-latam-pmd29-70-81.html
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETAIL/
I used adb flash tools as the method in flashfile.xml inside the rom.
my device:
Click to expand...
Click to collapse
You should be using
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETBR/
Sent from my ali using XDA Labs

sd_shadow said:
You should be using
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETBR/
Click to expand...
Click to collapse
I already installed all these RETBR roms. None started. when the Motorola logo appears, the device restarts.

I was searching the net and I found some articles saying that it could be because the processor is MIDIATEK (MT6771V / WL). AND THAT WOULD HAVE TO DOWNLOAD MTK / Sp flashing tools:
https://flashtool.org/5/download-sp-flash-tool.html
to install the rom on devices with this processor.
then I installed this program, but it needs the rom to have a file called "mt6771-scatter- android-file.txt "- what my device's roms don't have.
So I found a program that would generate this file (mt6xxx -scatter-android-file.txt):
https://mega.nz/file/YAogUAAL#cAbYxrWcUODmyVLD6p2Oz-YTsxm9Fb61A0RUq6OmkYI
but as nothing is so easy in this life, the program does not identify my device. not even after I installed the MidiaTek drivers (MTK drivers):
I don't know what to do.

I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot

adrianosk8 said:
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0 fastboot flash -u system_a system.img_sparsechunk.1 fastboot flash -u system_a system.img_sparsechunk.2 fastboot flash -u system_a system.img_sparsechunk.3 fastboot flash -u system_a system.img_sparsechunk.4 fastboot flash -u system_a system.img_sparsechunk.5 fastboot flash -u system_a system.img_sparsechunk.6 fastboot flash -u system_a system.img_sparsechunk.7 fastboot flash -u system_a system.img_sparsechunk.8 fastboot flash system_b system_other.img_sparsechunk.0 fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
did it work? and could you install magisk after that?

Matiasfh01 said:
did it work? and could you install magisk after that?
Click to expand...
Click to collapse
Yes, It does. But i don't install the magisk after that because i don't want It happend the same error.

adrianosk8 said:
Yes, It does. But i don't install the magisk after that because i don't want It happend the same error.
Click to expand...
Click to collapse
can u poste the final flashfile here pls

Matiasfh01 said:
can u poste the final flashfile here pls
Click to expand...
Click to collapse
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot

Watter flash het u gebruik?

adrianosk8 said:
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
i need the firmware i use to fix the xt2015-2 please brother I could not solve
I could not solve

adrianosk8 said:
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
you have saved my phone Bro!
this works..

Does anyone have the controls for the moto g 8 xt2045-1 to flash the stock rom?

BrenoSilva1997 said:
Does anyone have the controls for the moto g 8 xt2045-1 to flash the stock rom?
Click to expand...
Click to collapse
You can use LMSA to flash g8 stock rom

adrianosk8 said:
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
hello, I know this is more than I year old but still I wanted to thank you for posting this solution, I was having a really hard time trying to fix my mom's phone and just with this all got solved, thank you

adrianosk8 said:
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
i love u

[SOLVED] LineageOS stuck at first boot (moto G5 xt1676)

Hello everyone,
I just got a Moto G5 (on a refurbishment store) that works perfectly fine with stock OS.
My goal is to install lineageOS on it.
I managed easily to :
- unlock bootloader
- install TWRP (3.5.2_9.0) or the lineageOS recovery
- install lineageOS images and associated opengapps (pico) or mindthegapps
But on every attempt, at first lineageOS boot, it gets stuck (the blue bubble goes along the line for 45 minutes until it automatically goes back to recovery).
I tried many different combinations :
- twrp + lineageOS 18.1, with MindTheGapps (arm64 for Android 11)
- lineageOS rcovery 18.1 + lineageOS 18.1, with or without MindTheGapps
- twrp + lineageOS 17.1, with or without the corresponding OpenGapps pico package
When using TWRP at first i left TWRP system app option checked, but afterwards I always verified the option to NOT install it (i've read that it's a common cause for the problem).
All these combinations lead to the same result : 45 minutes waiting, back to recovery. I even tried to wait several times 45 minutes (up to 3 reboots, and after 2 reboots do a factory reset as suggested by lineageOS recovery).
So my questions :
- is there a way to know what LineageOS has been doing all this time ? Some log file i could access from recovery or fastboot mode ?
- is there an alternative ROM you would advise me to try ?
Ah, and last but not least, results of fastboot getvar all (with some xxx replacing what i thought could be sensitive data) :
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.25
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: xxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: xxx
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxx
(bootloader) meid:
(bootloader) date: 05-09-2017
(bootloader) sku: XT1676
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 24 1:56: 9 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPPS25.
(bootloader) ro.build.fingerprint[1]: 137-93-12/18:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.321.18.cedric.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband[0]: M8937_22.29.02.56.01R CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4a0c859 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Wed May 2 06:29:31 CDT
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.25-0-g0cc8007
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=87b19b9-dirty
(bootloader) devcfg.git: git=87b19b9-dirty
(bootloader) keymaster.git: git=87b19b9-dirty
(bootloader) cmnlib.git: git=87b19b9-dirty
(bootloader) cmnlib64.git: git=87b19b9-dirty
(bootloader) prov.git: git=MBM-NG-VB8.09-0-g1a41aff
(bootloader) aboot.git: git=MBM-NG-VB8.25-0-gb74f6bf
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above

Looks like you are trying to flash the rom on an old stock firmware image
Make sure you are on the latest retail firmware version
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Flash firmware via following terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Start device normally to make sure it boots
Flash twrp
In twrp go to wipe and format data (option to the right of advanced wipe)
Restart back to twrp recovery
Wipe advanced wipe - system data cache
Install rom zip
Install gapps (arm64 nano android 10 or 11 depending on what rom)
Install magisk (optional for root)
Wipe delvik cache
Restart

Yes, that did solve the problem !
Thanks a lot for you detailed reply.

TheFixItMan said:
Looks like you are trying to flash the rom on an old stock firmware image
Make sure you are on the latest retail firmware version
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Flash firmware via following terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Start device normally to make sure it boots
Flash twrp
In twrp go to wipe and format data (option to the right of advanced wipe)
Restart back to twrp recovery
Wipe advanced wipe - system data cache
Install rom zip
Install gapps (arm64 nano android 10 or 11 depending on what rom)
Install magisk (optional for root)
Wipe delvik cache
Restart
Click to expand...
Click to collapse
I updated to Lineage 18.1 on my moto g5 and the fingerprint gestures don't work anymore.
What do I do now? I've tried downgrading to an earlier ROM (DOT) but it the fingerprint gestures doesn't work anymore on that either.

HB-2021-III said:
I updated to Lineage 18.1 on my moto g5 and the fingerprint gestures don't work anymore.
What do I do now? I've tried downgrading to an earlier ROM (DOT) but it the fingerprint gestures doesn't work anymore on that either.
Click to expand...
Click to collapse
Use the correct firmware for the correct rom
Any rom based on oero firmware requires oreo firmware for the fingerprint to work
Any rom based on Nougat firmware requires Nougat firmware for the fingerprint to work
Note if downgrading to a Nougart based rom all you have to flash is fsg.mbn from Nougart firmware
If you are flashing an oreo based rom I recommend flashing all of the latest retail oero firmware

TheFixItMan said:
Use the correct firmware for the correct rom
Any rom based on oero firmware requires oreo firmware for the fingerprint to work
Any rom based on Nougat firmware requires Nougat firmware for the fingerprint to work
Note if downgrading to a Nougart based rom all you have to flash is fsg.mbn from Nougart firmware
If you are flashing an oreo based rom I recommend flashing all of the latest retail oero firmware
Click to expand...
Click to collapse
Where can I download the oreo firmware to revert back to Oreo?

HB-2021-III said:
Where can I download the oreo firmware to revert back to Oreo?
Click to expand...
Click to collapse
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

I am interrested by stock oreo firmware for moto g 5 (cdric) XT1676 too.
but the mirror is empty now (the 10th of february 2022)
Edit;
the files have been moved to another mirror at https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/cedric/official/

Moto G7 Power bootloop after flash stock firmware

My little sister gave me his phone because it was looping at bootlogo
I've flashed some firmwares before so i tried to fix it. I downloaded this firmware: https://mirrors.lolinet.com/firmware/moto/ocean/official/AMXMX/
and tried to flash it but i didn't work. Still bootlooping, tried with blankflash but none of this versions did anything, just <waiting for device> Blankflash i used: https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/
i realized that the battery level screen don't displays anymore. when i connect it it's looping at electricity logo
Variables i think might know
version: 0.5
version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-210201
product: ocean
secure: yes
securestate: oem_locked
factory-modes: disabled
iswarrantyvoid: no
max-download-size: 536870912
imei: [I hide it for security but i got one]
carrier_sku: XT1955-2
ro.carrier: amxmx
running-boot-lun: 0
slot-successful:_a: No
slot-successful:_b: No
slot-bootable:_a: No
What could i do?

Lol, i just solved it
Tried with Lenovo/Moto smart assistant : https://support.lenovo.com/us/en/downloads/ds101291
Flashed but not worked at all (but It's an important step), then i downloaded https://drive.google.com/file/d/1LzWEzxSbg56GqIZaVHj8WxbuTMNWfzKb/view
and ran this commands on cmd
fastboot flash devcfg_a devcfg.mbn
fastboot flash devcfg_b devcfg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash dsp_b adspso.bin
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash pmic_a pmic.elf
fastboot flash pmic_b pmic.elf
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
fastboot flash splash splash.img
fastboot flash tz_a tz.mbn
fastboot flash tz_b tz.mbn
fastboot flash xbl_a xbl.elf
fastboot flash xbl_b xbl.elf
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot erase userdata
Not all commands worked but cmd skip those, then the phone worked again
I got a problem with the IMEI (I'ts 'unknow') but i can't flash another NON-HLOS.bin file (The correct for my firmware version)
At least it works for wifi usage