Develop Bugs

Bought a bricked XT1789-06 for cheap

Good morning,
I bougth a X1789-06 for cheap on ebay and thought I can fix it. But its harder then I expected.
The system doesn't start at all, except fot the bootloader. I'm able to run fastboot but I can't do much there because it's locked. ADB is not avavailable.
Here is my fastboot getvar all:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_SS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565180808xxxxxx
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3773
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-180828
(bootloader) git:tz: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:storsec: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:prov: MBM-3.0-nash_retail-22c9393-190327
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 3
all: listed above
finished. total time: 0.172s
I tried to do fastboot boot boot.img with the rom thats in "ro.build.fingerprint" but it doesn't boot. Neither does TWRP.
The result at booting into TWRP looks like that:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_SS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot boot twrp-3.2.3-2-nash.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 30.773s
LMSA also doesnt work. It says "Flash failed. Please try again".
Do you have any ideas how to get out of this and get something runnung again?
Thanks
Benny

bennyschw said:
Good morning,
I bougth a X1789-06 for cheap on ebay and thought I can fix it. But its harder then I expected.
The system doesn't start at all, except fot the bootloader. I'm able to run fastboot but I can't do much there because it's locked. ADB is not avavailable.
Here is my fastboot getvar all:
I tried to do fastboot boot boot.img with the rom thats in "ro.build.fingerprint" but it doesn't boot. Neither does TWRP.
The result at booting into TWRP looks like that:
LMSA also doesnt work. It says "Flash failed. Please try again".
Do you have any ideas how to get out of this and get something runnung again?
Thanks
Benny
Click to expand...
Click to collapse
Looks like getvar all says Retail
But you are flashing Reteu?
Try
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
Sent from my mata using XDA Labs

Goot moring,
tried to flash this version with the flashall tool, same result.
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.222s]
finished. total time: 0.222s
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.240s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.302s
Those lines above are the first ones with the flashall tool. Flash permission is always denied so nothing changes.
When I try to boot via fastboot boot boot.img the Motorola Logo appears for 30 secounds and then goes to fastboot again.
The problem is, that flasing is locked and I need to unlock it somehow. But its not possible without some Android system running because I have to activate it in the developer options.
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem unlock RXNDLVGJRXZ65Y62EZUE
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
I dont know witch strange things happend to this poor phone.
But thank you for your reply.
Benny

Since of locked status you can't change bootloader at moment. So don't try to flash an OS version different from actual bootloader (Nougat?)
Flash an OS version "compatible" with boot loader (don't try to flash bootloader!!), boot to system, switch to unlockable status, unlock it and... enjoy!
Remember anyway thay since you have fastboot access it isn't still hardbricked at all...

enetec said:
Since of locked status you can't change bootloader at moment. So don't try to flash an OS version different from actual bootloader (Nougat?)
Flash an OS version "compatible" with boot loader (don't try to flash bootloader!!), boot to system, switch to unlockable status, unlock it and... enjoy!
Remember anyway thay since you have fastboot access it isn't still hardbricked at all...
Click to expand...
Click to collapse
What makes me suspicious is that it says "RETAIL" in the fingerprint but I have the German/Europe version. So it should be "RETEU".
Anyway, tried to flash the 7.1.1 retail stock rom because theres no reteu 7.1.1 available but the result is still the same: "Permission denied". But it was worth a try!
"Fastboot boot boot.img" doesn't work either. Bootscreen appears for a while, it vibrates and then goes back to fastboot.

I have a European z2 and it's retail version.
When it bootloop I flashed wrong firmware retu. Had the ADB debug not available and bootloader locked.
Then power and volume down I read the right version and downloaded the ROM and flashed it whit error but it worked.
Try flash this one https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

berka38 said:
I have a European z2 and it's retail version.
When it bootloop I flashed wrong firmware retu. Had the ADB debug not available and bootloader locked.
Then power and volume down I read the right version and downloaded the ROM and flashed it whit error but it worked.
Click to expand...
Click to collapse
How do I know whats the right version for my bootloader? Just by trial and error?
Ist there a list somewhere?
But yes, there is some hope rising inside me
EDIT:
I tried the rom you suggested already. It dowsn't work. Same error as always: Permission denied.

I got to check how I find my info what was on it later but it also gave me error when flashed but It booted

berka38 said:
I got to check how I find my info what was on it later but it also gave me error when flashed but It booted
Click to expand...
Click to collapse
Nope, tried it again. While flashing there are those known permission denied errors. When it should boot the "device is corrupt" screen shows up and it shuts down after a while.
But the slots changed somehow:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565180808xxxxxx
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3760
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:pmic: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190705
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:prov: MBM-3.0-nash_retail-3537781-190705
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.274s
EDIT:
Uh, I noticed that the bootloader has also changed. Don't know whats happening here.
EDIT 2:
Is there a way to "hardbrick" the phone on purpose to do a blankflash?

bennyschw said:
Nope, tried it again. While flashing there are those known permission denied errors. ...<CUT>
Click to expand...
Click to collapse
Since what you posted you have an Oreo Reteu flashed on this phone. More, it is reported verity off and warranty void, so your bootloader should be unlocked.
My suspect is that someone has flashed it with Oreo THEN tried to relock bootloader and... bricked it! :silly:
Anyway, i don't know bootloader versions, but if this has been already flashed with Oreo, I don't think you will be able to reflash it with Nougat easily...
So, I would try this way...
- try to oem unlock it and look what it says...
- try to flash it with Oreo RETEU or Oreo Retail and look what happens...
What is weird is that "flashing locked" status...

You should try the lmsa tool first, see if it will do a rescue and get you back to booting.
https://support.lenovo.com/us/en/downloads/ds101291
If no go, then you can try a blankflash. It's possible that between all the flashing there have become discrepancies in the boot chain, and a blankflash will fix that. Afterwards you flash the correct firmware for your phone. You have an -06 Dual Sim right? So you'll probably want reteu ds firmware, but retail should also work. Either way it should boot, the only problem could be no modem. If that's the case, then factory reset from the recovery to see if that sorts it. If not, then flash the retail firmware and do a factory reset from the recovery, modem should be back.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
I would stay away from pie firmware until you're up and running. Just for verification it does say xt1789-06 by the charging port right? Does it have a dual sim try as well? Your priority should be, getting booting, sign into google, oem unlock. Once your bootloader is unlocked you'll have wiggle room, until then it'll be a little tough going.

Goot morning,
LSMA failes. It says "Fastboot flash single partition - Flash failes. Please try again.
When I do the oem unlock the phone replies:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem unlock RXNDLVGJRXZ65Y62EZUE
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.006s]
finished. total time: 0.007s
Now I just tried to flash the boot.img of RETEU:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.541s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.547s
And RETAIL:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.538s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.544s
In my first post I was trying to flash the single sim version. Was my fault. But the same things happend there. This is a XT1789-06 with dual sim.
But as you said, it should have booted with no mobile connection.
By the way, fastboot oem blankflash doesnt work either:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.005s
Is there another way to go to blankflash?
I also tired the edl cable method. But it went right into bootloader.
Right now I'm setting up my old laptop with only USB 2 ports. Maybe theres a difference. I'll keep you up to date.
Thank you for your effort!
Benny

This is the last retail oreo firmware, it appears to be newer than what you've tried or at least what has been shown from your getvar output.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Before you try and flash it, run getvar command again and note your build version, build fingerprint, and which slot is your current slot . Then try to flash the retail firmware and boot. If nothing seems to change run the getvar command again and see if there are any changes to what you noted before. If your current slot is different, run the flashall again. If the current slot is the same, then fastboot --set-active=other and faatboot reboot bootloader. Run getvar command again to verify that you're on the other slot, and note the items listed above. Then run your flashall again. Run getvar command one more time and note the items again.
Hopefully enough of that will flash so you can boot. Between what you've flashed and god knows what was flashed before you, there could be a hodge-podge of nonsense scattered between the slots.
If still no boot, try running the lmsa tool again, maybe enough was cleaned up for the tool to run. Make sure that you're using admin privileges for the tool and command prompt if needed.
*Note - oem unlock won't work until you've enabled oem unlocking in dev settings, which is why booting is your 1st priority.

41rw4lk said:
This is the last retail oreo firmware, it appears to be newer than what you've tried or at least what has been shown from your getvar output.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Before you try and flash it, run getvar command again and note your build version, build fingerprint, and which slot is your current slot . Then try to flash the retail firmware and boot. If nothing seems to change run the getvar command again and see if there are any changes to what you noted before. If your current slot is different, run the flashall again. If the current slot is the same, then fastboot --set-active=other and faatboot reboot bootloader. Run getvar command again to verify that you're on the other slot, and note the items listed above. Then run your flashall again. Run getvar command one more time and note the items again.
Hopefully enough of that will flash so you can boot. Between what you've flashed and god knows what was flashed before you, there could be a hodge-podge of nonsense scattered between the slots.
If still no boot, try running the lmsa tool again, maybe enough was cleaned up for the tool to run. Make sure that you're using admin privileges for the tool and command prompt if needed.
*Note - oem unlock won't work until you've enabled oem unlocking in dev settings, which is why booting is your 1st priority.
Click to expand...
Click to collapse
Absolutely nothing has changed except the battery voltage
Tried all the different retail and reteu 8.0 versions but there changes nothing. I also tried to boot the roms via boot boot.img but no one worked.
LSMA replies with the same error as before.
Cant even change the slots manually:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot --set-active=other
Setting current slot to 'b'...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot --set-active=b
Setting current slot to 'b'...
FAILED (remote failure)
finished. total time: 0.006s
I think I bought this phone: https://forum.xda-developers.com/z2-force/help/bricking-support-questions-xt1789-06-t3995049
:silly:
Anyway, my hope is not gone!
Thank you
Benny

adb-fastboot_ver29.0.5
Attached is the latest adb/fastboot files pulled from androidsdk. It's weird that you can't even switch slots, so here is the latest files, just unzip to their own folder. Open folder, hold shift then right-click a blank area in the folder, open command window here. Try repeating the instructions in my last post and see if anything works this time around, use a 2.0 port if possible and use a port off the motherboard. Trivial it seems, but necessary for some. Double check the command fastboot --setactive="a,b, or other" could be "_a or _b" I don't use that command often so the syntax could be wrong, so try with or with the underscore_ or simply use 'other' w/o 'quotes' to switch slots. We're trying to get the slots as matched as possible so that if all else fails hopefully the lmsa tool will at least do a rescue on it. Right now I think you have bits and pieces of everything and lmsa sees it as something foreign or custom and won't touch it.

bennyschw said:
I think I bought this phone: https://forum.xda-developers.com/z2-force/help/bricking-support-questions-xt1789-06-t3995049
:silly:
Anyway, my hope is not gone!
Thank you
Benny
Click to expand...
Click to collapse
I thought you were being funny until I looked at the serial no. in both posts... it the same f'n phone. Flashed to pie, f'd up, rolled back to oreo, bootloader locked, all kinds of wrong. Since it was on pie before, you'll need pie to fix it. Depending on what version of pie was flashed, you might need to wait for an update to roll out so you have a new enough firmware to overwrite the nv values. So there's that.

Well, that how it is now. I'll let it sit for a while, maybe sonething changes or I have some new ideas
But I'm happy about every new suggestions from you.
Thanks for your help!
Benny

bennyschw said:
Well, that how it is now. I'll let it sit for a while, maybe sonething changes or I have some new ideas
But I'm happy about every new suggestions from you.
Thanks for your help!
Benny
Click to expand...
Click to collapse
Did you succeed benny?
I'm practically having the same problem.
but when I try to change the slot with the command "fastboot --set-active = b"
the error appears: fastboot: error: Device does not support slots

danyfenton said:
Did you succeed benny?
I'm practically having the same problem.
but when I try to change the slot with the command "fastboot --set-active = b"
the error appears: fastboot: error: Device does not support slots
Click to expand...
Click to collapse
The same situation here, I am stuck in the bootloader because it indicates "Flashing_lock", I cannot enter the operating system to unlock because it says that the device is corrupt, I cannot change the slot in Fastboot mode, I cannot flash a new ROM, Neither the same ROM or the old ROM ... What do you think about forcing the EDL state, to try to recover with blankflash? (If I already tried the blankflash commands and do not allow them in the Fastboot, I would have to damage the cell phone on purpose but I don't know how)

and you haven't achieved anything yet have you?
mine is still standing here.

Moto G8 stuck on boot screen 'M' but goes no further

So, I have just acquired a secondhand phone Moto G8, sticks at the M boot up screen and goes no further. I can access fastboot and the PC recognises it, and can access stock recovery and factory reset. Just does the same. Tried the moto firmware repair tool but didn't recognise the phone was connected (despite fastboot working). Thought about unlocking the bootloader but I get a failure when I request the unlock info in fastboot, so can't get the unlock code. Ideas? If I could unlock the bootloader I could manually flash the stock firmware.
I downloaded the official firmware from lolinet - which is basically this: XT2045-2_RAV_RETEU_10_QPJS30.63-35-1-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml This is showing as correct on the bootloader screen, but to be sure I ran fastboot getvar: (bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-rav_reteu-dfa2a6b4b2-210101
(bootloader) product: rav
(bootloader) board: rav
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY227BHF38
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: FC48029A
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805259264
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxx
(bootloader) imei2: xxxxx
(bootloader) meid:
(bootloader) date: 04-13-2020
(bootloader) sku: XT2045-2
(bootloader) carrier_sku: XT2045-2
(bootloader) battid: SB18C51711
(bootloader) battery-voltage: 4298
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/rav_reteu/rav:10/QPJS30.6
(bootloader) ro.build.fingerprint[1]: 3-35-1-17/80ecc:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Fri Jan 1 11:0
(bootloader) kernel.version[3]: 2:34 CST 2021
(bootloader) git:abl: MBM-3.0-rav_reteu-dfa2a6b4b2-210101
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C68387
So I know I've got the right firmware.

https://forum.xda-developers.com/t/moto-g-fast-rav-i-bricked-my-device.4247149/post-84657525 would this maybe work?

GitManMatt said:
https://forum.xda-developers.com/t/moto-g-fast-rav-i-bricked-my-device.4247149/post-84657525 would this maybe work?
Click to expand...
Click to collapse
Just tried to flash twrp recovery (different one to listed but probably wouldn't make a difference) got this:
fastboot flash recovery twrp-rav.img target reported max download size of 805259264 bytes
sending 'recovery' (42408 KB)...
OKAY [ 0.912s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.936s
I'll try the suggested one, probably won't be any different

GitManMatt said:
Just tried to flash twrp recovery (different one to listed but probably wouldn't make a difference) got this:
fastboot flash recovery twrp-rav.img target reported max download size of 805259264 bytes
sending 'recovery' (42408 KB)...
OKAY [ 0.912s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.936s
I'll try the suggested one, probably won't be any different
Click to expand...
Click to collapse
nope same message

NVM - I worked it out - used the mfastboot tool rather than fastboot, and plugged these commands in:
.\mfastboot getvar max-sparse-size
.\mfastboot oem fb_mode_set
.\mfastboot flash partition gpt.bin
.\mfastboot flash bootloader bootloader.img
.\mfastboot flash vbmeta vbmeta.img
.\mfastboot flash radio radio.img
.\mfastboot flash bluetooth BTFM.bin
.\mfastboot flash dsp dspso.bin
.\mfastboot flash logo logo.bin
.\mfastboot flash boot boot.img
.\mfastboot flash dtbo dtbo.img
.\mfastboot flash recovery recovery.img
.\mfastboot flash super super.img_sparsechunk.0
.\mfastboot flash super super.img_sparsechunk.1
.\mfastboot flash super super.img_sparsechunk.2
.\mfastboot flash super super.img_sparsechunk.3
.\mfastboot flash super super.img_sparsechunk.4
.\mfastboot flash super super.img_sparsechunk.5
.\mfastboot flash super super.img_sparsechunk.6
.\mfastboot flash super super.img_sparsechunk.7
.\mfastboot flash super super.img_sparsechunk.8
.\mfastboot flash super super.img_sparsechunk.9
.\mfastboot flash super super.img_sparsechunk.10
.\mfastboot flash super super.img_sparsechunk.11
.\mfastboot flash super super.img_sparsechunk.12
.\mfastboot flash super super.img_sparsechunk.13
.\mfastboot erase carrier
.\mfastboot erase userdata
.\mfastboot erase metadata
.\mfastboot erase ddr
.\mfastboot oem fb_mode_clear
I did this manually but you can use the firmware guide elsewhere to run a batch file which will do it for you (I just preferred methodically going through each one by one!)
All back and up and running now. Please ask if you need help, I might be able to suggest something now!

Hello, I have the same moto g8 and I have not been able to solve anything as you could, the command already downloads the mfastboot and it does not recognize anything, we are already in android 11 and change this partition is not there. \ mfastboot flash super super.chunkg.11_sparsechunk.8 and this up to super 15 will you help me?

Adrianbene said:
Hello, I have the same moto g8 and I have not been able to solve anything as you could, the command already downloads the mfastboot and it does not recognize anything, we are already in android 11 and change this partition is not there. \ mfastboot flash super super.chunkg.11_sparsechunk.8 and this up to super 15 will you help me?
Click to expand...
Click to collapse
Hi there, so I figured out how to flash this thing a while back but it can be a nightmare to reset. First, you should try lenovo rescue agent to see if it can fix it, most of the time, the software can fix anything you've done. If that doesn't work, you only have one option left. You have to flash chunks in fasboot to reset, which isn't to hard. Now if you are trying to flash a custom rom to this phone you have to first have android 10 stock flashed with a password in place, with no numbers. I use a simple word like five. The reason is you cant unlock system and decrypt it if it has nothing to decrypt in twrp. You can flash in a custom recovery otherwise though, likes lineages custom recovery thats built for this phone. The other issues you are going to run into are making sure your using the right build, there's like 20 for this phone because it was built out and sold as a bunch of different models so it has a bunch of stock roms. If your phone is unlocked use the retus in lolinet and flash chunks. It's best to flash custom roms ontop of a stock android 10 in fastbootD with this phone, regardless if youve been told to use twrp or not, imo.

XT-1675 with locked bootloader [HELP]

Hi,
I have a cedric xt-1675 with locked bootloader (i have a key to unlock and i tried unlocking it through fastboot it says its disable) and when I try to load into recovery mode it gave me error
FAILED TO PASS VALIDATION. BACKUP TO FASTBOOT
BOOTUP FAILED
I tried flashing firmware through fastboot white doing mfastboot flash partition gpt.bin
C:\Users\Abdul Rafy\Desktop\New folder\ar\boot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.077s
all other flash commands works fine except mfastboot flash partition gpt.bin
Thanks

You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options

TheFixItMan said:
You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options
Click to expand...
Click to collapse
thanks for the reply, I never have unlocked my device before it has locked bootloader since start. anyway, I have tried "fastboot oem unlock UNLOCK_KEY" it says enable oem unlocking from developer option and the problem is i couldn't get into phone not even into recovery just fastboot. It used to get stuck at moto logo but now when I try to boot normally it says
Failed to verify hab image boot
failed to validate boot image
Error: Failed to pass validation. backup to fastboot
Boot up failed
and if I try to go into recovery, it says
Failed to verify hab image recovery
failed to validate recovery image
Error: Failed to pass validation. backup to fastboot
Boot up failed
another thing I did try Software repair assistant but it gave me error on 47%

Here the getvar just in case:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A4 FV=00000000000000A4
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x4e
(bootloader) uid: 0295944600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Last time flashing failed
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 03-07-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 8: 2: 8 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-19-4-2/3447de:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.301.2.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_46.42.02.75R CEDRIC_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0001
(bootloader) kernel.version[1]: 6-g6e15bdb ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Mon Mar
(bootloader) kernel.version[3]: 4 18:13:35 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3f87a46
(bootloader) devcfg.git: git=3f87a46
(bootloader) keymaster.git: git=3f87a46
(bootloader) cmnlib.git: git=3f87a46
(bootloader) cmnlib64.git: git=3f87a46
(bootloader) prov.git: git=3f87a46
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tescogb
(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

This is because the boot.img you flashed is not signed by Motorola and its failing to pass verification
If you were trying to unlock the bootloader you should have followed the correct process and enabled adb and oem unlock from the dev options
Never flash firmware on a locked bootloader - if it goes wrong you have no chance of correcting it
You basically have two options now
Try and find firmware that will flash fully on your device
Firmware can be found here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
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
Or take to a repair shop for either a motherboard replacement or if possible flashing with a jtag

Cedric XT-1676 firmware error:

ERROR: This package requires from an Android 8.1 stock ROM build.
Such a bug prevents me from updating the lineage-18.1-20220116-microG-cedric.zip image to a newer version,
e.g. lineage-18.1-20220301-microG-cedric.zip
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(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: ZYxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: AADB0F5700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-20-2018
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 1:17:47 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8937_22.29.02.69.01u CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(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.061s
I installed the stock rom via fastboot from the image:
CEDRIC_OPPS28.85_13_6_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
using this commands:
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
Click to expand...
Click to collapse
I installed TWRP, wiped the / system partition, / data, / cache,
then I installed lineage-18.1-20220116-microG-cedric.zip + Magisk.
the system is working fine.
However, the update to lineage-18.1-20220301-microG-cedric.zip stops on a bug with the firmware version.
I download lineage images from here:
cedric
Cheers

Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com

TheFixItMan said:
Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Click to expand...
Click to collapse
Thank you very much for that firmware link... I was ready to give up.
Oddly, the official Motorola Repair tool does not install a Lineage-friendly version of the stock firmware.
If it helps any other noob, I used this site to install the stock firmware:
Install Stock Firmware on Moto G5 via Fastboot Commands
In this comprehensive tutorial, we will show you how to install stock firmware on Motorola Moto G5 via Fastboot commands and unbrick it.
www.droidwin.com

Hi
I Installed via fastboot:
CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
After this operation, my Cedric does not have a unique IMEI number.
As a result, the SIM card does not work at all, I can only make emergency calls.
fastboot getvar all 2>&1| grep -i imei
(bootloader) imei: 356476085352435
I tried to fix IMEI according to this thread:
Moto G5 Cedric - Repair Imei = 0
After being in a LineageOS ROM, I decided to reinstall the Stock Firmware od Moto G5 Cedric through ADB, but after that the phone signal was lost, and both IMEI appear in 0, Has anyone else had that problem, or know the solution?
forum.xda-developers.com
I did several times (after installing stock ROM, after installing LineageOS, after installing LineageOS-microg):
fastboot erase modemst1; fastboot erase modemst2 ; fastboot erase cache
Erasing 'modemst1' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'modemst2' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'cache' OKAY [ 0.017s]
Finished. Total time: 0.020s
However, to no avail, the phone has no IMEI number on any SIM card.
It seems the XT1676 European version is more resistant to IMEI repair attempts.
Cheers

My IMEI was also zeroed by the stock ROM.
I tried using the recommendations in the following link, but I was ultimately unable to recover the IMEI from within the stock rom. Flashing LOS worked.
Moto g5 plus IMEI 0 after flashing anything? Read on!
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required! Prerequisites: U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on...
forum.xda-developers.com

Same here. Unable to recover IMEI for XT1676. The suggested procedure just does not work in this phone version with latest stock ROM OPP28.85-19-4-2.

Question Soft brick on unmodded XT2052-1. "No bootable A/B slot"

Hi all. I'm a complete newb to this, so please excuse any incorrect terminology. I appreciate any help given!
Here's the situation in brief:
This Moto E (XT2052-1) is completely unmodded. Nothing rooted, nothing unlocked, nothing flashed before. About 1.5 years in use.
It goes through a bootloop, and then "falls through to fastboot."
It reports "No bootable A/B slot" and fastboot getvar current slot yields "not found". I can't get it to switch to either slot.
can't find current slot
Code:
C:\platform-tools>fastboot getvar current slot
(bootloader) current: not found
getvar:current FAILED (remote: '')
fastboot: usage: unknown command slot
can't assign a slot
Code:
C:\platform-tools>fastboot set_active a
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
I think flashing stock ROM (specifically the boot image?) will fix the issue, but I'm running into problems
doesn't let me flash boot image, needs vbmeta image
Code:
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.764s]
Writing 'boot_a' (bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing boot image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
trying boot with boot image without flashing
Code:
C:\platform-tools>fastboot boot boot.img
Sending 'boot.img' (32768 KB) OKAY [ 0.765s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
And then flashing the boot image again after flashing the vbmeta image (... successfully? not sure)
Code:
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.768s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
I'm not sure if I'm missing a step, or if I need to change toggle a setting somewhere, or what.
I don't want to wipe it, but I understand it might prove to be necessary.
Here are the nitty gritty details:
It started bootlooping and then "falling back to fastboot" about 3 days ago. I don't think there was any damage or instigating event. It says to connect to a computer to fix it with "Software Repair Assistant" (which doesn't seem to exist). Here's the "Bootloader logs" text after turning it on and attempting to start it:
Start Up Failed:​Your device didn't start up successfully.​Use the Software Repair Assistant on computer to repair your device.​Connect your device to your computer to get the Software Repair Assistant.​you can try to press powerkey in failure interface to fix it [sic]​If you try to fix it, Please try it at least 6 times [sic]​
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux,falling back to fastboot
Fastboot Reason: Fall-through from normal bootmode
No bootable A/B slot
Failed to boot Linux,falling back to fast bootmoode
Boot up failed
Click to expand...
Click to collapse
Many guides say to use LMSA to detect and fix, but I've also seen people warning of it flashing incorrectly, so I'm wary of it.
The problem seems to be with the A/B slot, so I've done research to understand what that means. I found this guide from droidwin.com useful, and have managed to do the following:
Downloaded and unzipped SDK platform tools.
I'm barely familiar with command line, but fastboot has been fine.
Tried fastboot set_active a, as well as b and other
Found appropriate (I think) stock ROM from here. It has the boot image, as well as many other files. I'm not familiar with how ROM is packaged.
Tried to flash the boot image from the stock ROM. It said I needed to flash the vbmeta image first.
Flashed the vbmeta image, onto both vbmeta_a and vbmeta_b (after much trial and error)
This took a while because I actually got ahold of and downloaded... let's say several stock ROM packages. Cycled through until I found one that was actually accepted.
Tried flashing the boot, but now Preflash validation failed
Here are all the relevent outputs from the command line
Code:
C:\platform-tools>fastboot devices
[...omitted...] fastboot
C:\platform-tools>fastboot getvar all
[...Let me know if I omitted something important...]
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: [...omitted...]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 101ECD4600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: [...omitted...]
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-10-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66367
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 6 2:44:35 UTC 2021" [idk why it says that time]
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-141-15-2/e9f0a:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.04R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[3]: pr 1 01:56:14 CDT 2022
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 0.233s
C:\platform-tools>fastboot set_active a
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot set_active other
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot set_active b
Setting current slot to 'b' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot getvar current slot
(bootloader) current: not found
getvar:current FAILED (remote: '')
fastboot: usage: unknown command slot
C:\platform-tools>fastboot getvar product
product: ginna
Finished. Total time: 0.003s
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.764s]
Writing 'boot_a' (bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing boot image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot: error: Failed to identify current slot
C:\platform-tools>fastboot getvar has-slot:vbmeta
has-slot:vbmeta: yes
Finished. Total time: 0.005s
C:\platform-tools>fastboot flash vbmeta vbmeta.img
fastboot: error: Failed to identify current slot
C:\platform-tools>fastboot boot boot.img
Sending 'boot.img' (32768 KB) OKAY [ 0.765s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot boot_a boot.img
fastboot: usage: unknown command boot_a
C:\platform-tools>fastboot boot_b boot.img
fastboot: usage: unknown command boot_b
C:\platform-tools>fastboot flashing unlock
(bootloader) This command requires you to first unlock the bootloader.
(bootloader) A unlock code may be required.
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot getvar iswarrantyvoid
iswarrantyvoid: no
Finished. Total time: 0.004s
[--WITH WRONG ROM--]
C:\platform-tools>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
[--WITH CORRECT ROM--]
C:\platform-tools>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_a' OKAY [ 0.006s]
Finished. Total time: 0.064s
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.768s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (32768 KB) OKAY [ 0.759s]
Writing 'boot_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_b vbmeta.img
Sending 'vbmeta_b' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_b' OKAY [ 0.006s]
Finished. Total time: 0.063s
C:\platform-tools>fastboot BE NORMAL PLEASE
fastboot: usage: unknown command BE
That's about what I've got so far. At one point I did fastboot reboot fastboot and got into fastbootd, but I had no idea what I was doing there and promptly left.
I'm almost ready to give in and try factory resetting it, but I feel like I'm just missing a piece of the puzzle. Maybe several. I don't know. I have so many tabs open.
Again, any help you can give is welcome! Please keep in mind, I only started learning about any of this yesterday (brand new words in my repertoire: image, flash, bootloader, fastboot, slot, stock, ROM, RETUS, NFC, and much, much more!). I may not be the most articulate, but I'm certainly trying :^)
[Edit: and let me know about any formatting faux pas I may have committed! With text color or code blocks or whatever it may be. I messed with the options probably a little more than I should have, heh]

Alright, I've done some more reading and tried a couple other things.
This post with a similar problem suggested that it was a faulty partition, and to run:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
This is what I got
Code:
C:\platform-tools>fastboot oem fb_mode_set
OKAY [ 0.002s]
Finished. Total time: 0.004s
C:\platform-tools>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.009s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.121s]
Finished. Total time: 0.252s
C:\platform-tools>fastboot oem fb_mode_clear
OKAY [ 0.002s]
Finished. Total time: 0.005s
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s
But it just did its normal bootloop after rebooting. [Oh wait, that's different... oh never mind. Just now, as I was writing, it stayed on one of the flashing screens for a significant amount of time, but then continued looping again]
WAIT OKAY, something happened! After the reboot from flashing gpt.bin, I tried flashing the boot image again.
Code:
[...directly after the previous commands...]
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.764s]
Writing 'boot_a' (bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing boot image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_a' OKAY [ 0.007s]
Finished. Total time: 0.054s
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.763s]
Writing 'boot_a' OKAY [ 0.908s]
Finished. Total time: 1.734s
It accepted the boot image! No more "Preflash validation failed"!
I immediately fastboot getvar all, and I really should have done so after flashing gpt.bin, but oh well. There are some changes!
Code:
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: [...omitted...]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 101ECD4600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [...omitted...]
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-10-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66367
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Apr 5 23:52: 0 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-141-15-2/e9f0a:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.04R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[3]: pr 1 01:56:14 CDT 2022
(bootloader) sbl1.git: MBM-2.1-ginna_retail-054f0bdd8c-220530
(bootloader) rpm.git: MBM-2.1-ginna_retail-20f2cf34-220530
(bootloader) tz.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) devcfg.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) keymaster.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) cmnlib.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) cmnlib64.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) prov.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) aboot.git: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 7
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 0.753s
First I noticed that the slots information had changed. There is now an active slot, and slot b now reads "bootable" (which is odd, because I flashed boot_a ), and a retry count that isn't 0! Then I noticed a bunch of the git variables also changed, to MBM-2.1-ginna_retail-[yaddayadda-yadda]
I have no idea what this means, but I call it progress!
________________________________________________________________​It still bootloops, but I'll keep poking at it.
A change I've notices, however, from even before I flashed gpt.bin, is an inconsistency of how it bootloops.
It either:
immediately falls through from normal bootmode
bootloops for a while and then goes into fastboot
bootloops and turns off
And I haven't really found a pattern why. I've taken to manually starting fastboot (with volume down) when before it would go there by itself. Who knows.

I'm sorry that I cant help with your situation but could you help me to understand these recovery options? My pc wont recognize the phone when connected in fastboot mode but the phone recognizes the pc....
what am I doing wrong? and are there any settings I'm supposed to have activated to facilitate the data transfer?
Here's my Forum post
Phone is completely stock btw

Heruktiang said:
I'm sorry that I cant help with your situation but could you help me to understand these recovery options? My pc wont recognize the phone when connected in fastboot mode but the phone recognizes the pc....
what am I doing wrong? and are there any settings I'm supposed to have activated to facilitate the data transfer?
Here's my Forum post
Phone is completely stock btw
Click to expand...
Click to collapse
Hi! Due to time constraints, I ended up fully flashing the stock ROM (thereby erasing userdata). I plan on updating this thread tonight with what I did, even though it just eventually led to erasing everything.
Hmm, as to your situation... I have to admit I am not familiar with all this (this was first time touching a bootloader, haha), but I took a quick look through your post. I can note a couple differences between our situations:
My recovery mode was inaccessible, as far as I could tell. If I tried to select it in the bootloader, I think it would give the same "No bootable A/B slot" error.
I never used the LMSA on the phone, but I did have it open when the phone was plugged in to the computer, and the bootloader logs indicated that some sort of communication was happening. I didn't record exactly what the commands were, but I think there were three, among them "getvar product" or some such.
Other than that, I have no insight on this. In my research, I found no way to get the userdata off a bootlooping phone that didn't have TWRP or some things (bootloader?) unlocked. Sorry I can't help much
I was wondering if the bootloop was prompted by a recent update, but there doesn't seem to be too many people affected

Thanks for the swift and detailed reply. I'm starting to think I was hacked. My gf admitted to hacking me before. Ill keep trying to get the pc to communicate with the phone.

GewdGrief said:
I plan on updating this thread tonight with what I did, even though it just eventually led to erasing everything.
Click to expand...
Click to collapse
Had you tried flashing with servicefile.xml from the your firmware archive? It flashes everything, but leaves userdata intact, so I think it would have been your best bet.