Develop Bugs

Moto z2 force xt1789-05 does not enter into recovery mode only stays in fastboot mode

My phone does not enter in recovery mode nor can I restore it from the factory, since it does not enter into recovery mode it only stays in fastboot, the last commands that it used were: adb kill-server and then fastboot -w, that's when the problem started, any solution? Thank you.

:good:

omnismart said:
:good:
Click to expand...
Click to collapse
does not enter into recovery mode, when I select recovery, it returns to fasboot mode

luiguy said:
does not enter into recovery mode, when I select recovery, it returns to fasboot mode
Click to expand...
Click to collapse
can you flash any recovery image and see if it enters the recovery after that?
It's possible that the is no recovery image in the recovery partition to boot hence it is taking back to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app

shibaa987 said:
can you flash any recovery image and see if it enters the recovery after that?
It's possible that the is no recovery image in the recovery partition to boot hence it is taking back to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
can be done by having the boot loader blocked?

luiguy said:
can be done by having the boot loader blocked?
Click to expand...
Click to collapse
you mean to say that you have a locked bootloader?
Sent from my [device_name] using XDA-Developers Legacy app

shibaa987 said:
you mean to say that you have a locked bootloader?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
that's right, and I'm in the stock ROM, the bootloader has never been unlocked

You keep posting the same question all over the place, but you're not helping anyone to help you. I've asked a couple times to see your flashfile, but it has never been posted. Maybe there is something wrong with it. We really need to try and flash the bootloader, that will tell us what we're up against. If you can flash the bootloader, then you can flash back to stock and get out of this mess, but if you get a permission denied and you're using an official signed, then that's another problem.
You said you've tried, but no you haven't. You've tried to use your flashfile and nothing happened, hence the reason I keep asking to see it. Your main goal right now, and I've said this before, is to determine whether you can flash or not. A locked bootloader will only accept official signed firmware from the same carrier with the same revision or higher. So pretty please, don't post the same question anymore but do post your flashfile so we can see if there is anything wrong with it. Better yet, if anyone has a working flashfile for the lastest -05 variant please post it so we can rule it out. In the meantime run this command in fastboot and post the output, but be sure that you don't post your imei info. Not trying to be a ****, but posting the same question all over the forum does nothing to help and will get you banned.
Code:
fastboot getvar all
Post the output of this command minus your imei info.

Code:
fastboot getvar all
Post the output of this command minus your imei info.[/QUOTE]
all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-b48569f-170628
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: no
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(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: NGRL470061
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 86027E05
(bootloader) securestate: engineering
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-29-2017
(bootloader) sku: XT1789-05
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4172
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_amx/nash:7.1.1/NPX26
(bootloader) ro.build.fingerprint[1]: .122-49/53:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.53.nash_amx.am
(bootloader) ro.build.version.full[1]: x.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.7.r1-09300-8x98.0
(bootloader) version-baseband: M8998_24.71.01.87R NRS
(bootloader) kernel.version[0]: Linux version 4.4.21-perf-gb6ca254 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 2015012
(bootloader) kernel.version[2]: 3 (prerelease) (GCC) ) #1 SMP PREEMPT We
(bootloader) kernel.version[3]: d Jun 28 08:50:20 CDT 2017
(bootloader) abl.git: MBM-3.0-nash_retail-b48569f-170628
(bootloader) xbl.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) pmic.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) rpm.git: MBM-3.0-nash_retail-d3e45a4-170628
(bootloader) tz.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) hyp.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) devcfg.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib64.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) keymaster.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) storsec.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) prov.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.146s

41rw4lk said:
You keep posting the same question all over the place, but you're not helping anyone to help you. I've asked a couple times to see your flashfile, but it has never been posted. Maybe there is something wrong with it. We really need to try and flash the bootloader, that will tell us what we're up against. If you can flash the bootloader, then you can flash back to stock and get out of this mess, but if you get a permission denied and you're using an official signed, then that's another problem.
You said you've tried, but no you haven't. You've tried to use your flashfile and nothing happened, hence the reason I keep asking to see it. Your main goal right now, and I've said this before, is to determine whether you can flash or not. A locked bootloader will only accept official signed firmware from the same carrier with the same revision or higher. So pretty please, don't post the same question anymore but do post your flashfile so we can see if there is anything wrong with it. Better yet, if anyone has a working flashfile for the lastest -05 variant please post it so we can rule it out. In the meantime run this command in fastboot and post the output, but be sure that you don't post your imei info. Not trying to be a ****, but posting the same question all over the forum does nothing to help and will get you banned.
Code:
fastboot getvar all
Post the output of this command minus your imei info.
Click to expand...
Click to collapse
there are the data that you asked me

What were you trying to do when all your trouble initially began? I see that you still have nougat on that slot and the bootloader secure state is engineering, that's not right. Can you still boot into your system? If so make sure adb is enabled. I assume oem unlock is greyed out and unavailable right? What firmware have you tried to flash? Also, if you're able to boot into your system you should disable fingerprint/lockscreen security until you have everything resolved.

41rw4lk said:
What were you trying to do when all your trouble initially began? I see that you still have nougat on that slot and the bootloader secure state is engineering, that's not right. Can you still boot into your system? If so make sure adb is enabled. I assume oem unlock is greyed out and unavailable right? What firmware have you tried to flash? Also, if you're able to boot into your system you should disable fingerprint/lockscreen security until you have everything resolved.
Click to expand...
Click to collapse
I just tried to update it to Android 8, if I can enter the system and I have USB debugging enabled, EOM is in gray, the ROM I wanted to install was: https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ . Android 8

luiguy said:
I just tried to update it to Android 8, if I can enter the system and I have USB debugging enabled, EOM is in gray, the ROM I wanted to install was: https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ . Android 8
Click to expand...
Click to collapse
In fastboot mode switch slots and run the getvar command again. Post the results and see if the other slot boots. If not switch back. You're currently on _a
Code:
fastboot devices
fastboot --set-active=b
fastboot getvar all
fasboot reboot
Post the results of the getvar command. If the phone boots to system on slot _b check out your settings, see if oem unlock is available and make sure adb debugging is on. If it doesn't boot, it should automatically fall back to slot _a but if it doesn't just run the commands above again only set active to a. You don't need to run the getvar command again once you're back to _a. *Note when you run the getvar command the 'current-slot' entry tells you what slot you're on.

41rw4lk said:
In fastboot mode switch slots and run the getvar command again. Post the results and see if the other slot boots. If not switch back. You're currently on _a
Code:
fastboot devices
fastboot --set-active=b
fastboot getvar all
fasboot reboot
Post the results of the getvar command. If the phone boots to system on slot _b check out your settings, see if oem unlock is available and make sure adb debugging is on. If it doesn't boot, it should automatically fall back to slot _a but if it doesn't just run the commands above again only set active to a. You don't need to run the getvar command again once you're back to _a. *Note when you run the getvar command the 'current-slot' entry tells you what slot you're on.
Click to expand...
Click to collapse
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-b48569f-17062
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: no
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: NGRL470061
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 86027E05
(bootloader) securestate: engineering
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-29-2017
(bootloader) sku: XT1789-05
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4301
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_amx/nash:7.1.1
(bootloader) ro.build.fingerprint[1]: .122-49/53:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.53.nash_
(bootloader) ro.build.version.full[1]: x.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.7.r1-09300-8x98.0
(bootloader) version-baseband: M8998_24.71.01.87R NRS
(bootloader) kernel.version[0]: Linux version 4.4.21-perf-gb6ca254
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 2
(bootloader) kernel.version[2]: 3 (prerelease) (GCC) ) #1 SMP PREE
(bootloader) kernel.version[3]: d Jun 28 08:50:20 CDT 2017
(bootloader) abl.git: MBM-3.0-nash_retail-b48569f-170628
(bootloader) xbl.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) pmic.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) rpm.git: MBM-3.0-nash_retail-d3e45a4-170628
(bootloader) tz.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) hyp.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) devcfg.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib64.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) keymaster.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) storsec.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) prov.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.193s

(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.193s
You're still on slot a, you need to be on slot b
After you run the command set-active, reboot the bootloader then do a getvar. Also, see if it will boot.
Code:
fastboot --set-active=b
fastboot reboot bootloader
fastboot getvar all
fastboot reboot

41rw4lk said:
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.193s
You're still on slot a, you need to be on slot b
After you run the command set-active, reboot the bootloader then do a getvar. Also, see if it will boot.
Code:
fastboot --set-active=b
fastboot reboot bootloader
fastboot getvar all
fastboot reboot
Click to expand...
Click to collapse
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'

luiguy said:
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
Click to expand...
Click to collapse
Either your fastboot file is out of date, or that engineering state is limiting your accessibility. Close any command prompt windows. Download this utilities zip, it has known good adb and fastboot files in it. Extract it to a folder somewhere, open the folder, hold shift and right click a blank area inside the folder, then choose open a command window here. Verify that your device is connected in fastboot 'fastboot devices', then try setting the active slot again and proceed from there.
*Note - Make sure you're using a 2.0 usb port off the motherboard, not a hub from the front of the pc and such. Most people don't have problems with this, but it has caused problems for some. Not all usb ports are so universal, ports on the mobo tend to have more consistent power supply and transfer rates; less interference as well.

41rw4lk said:
Either your fastboot file is out of date, or that engineering state is limiting your accessibility. Close any command prompt windows. Download this utilities zip, it has known good adb and fastboot files in it. Extract it to a folder somewhere, open the folder, hold shift and right click a blank area inside the folder, then choose open a command window here. Verify that your device is connected in fastboot 'fastboot devices', then try setting the active slot again and proceed from there.
*Note - Make sure you're using a 2.0 usb port off the motherboard, not a hub from the front of the pc and such. Most people don't have problems with this, but it has caused problems for some. Not all usb ports are so universal, ports on the mobo tend to have more consistent power supply and transfer rates; less interference as well.
Click to expand...
Click to collapse
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>

luiguy said:
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
Click to expand...
Click to collapse
It has to be your phone that limiting your commands. I ran the same commands right out of the utilities zip and had no troubles. I think since you can't really do anything else, and you can't flash back to stock normally you might need to blank flash to get the gist of things back in order. First though, I would open your flashall file and paste the lines one by one in the command prompt and see if you could manually flash your phone. As it stands now, whenever you try to run the .bat file it just does nothing. Skip the fb_mode set and the getvar and start with the actual flashing. It will either flash or you'll get a permission denied most likely.
If you can't manually flash the oreo firmware, then you'll most likely need to blank flash. Several people have had their phone go wonky after trying to upgrade from nougat. So much for seamless updates.

luiguy said:
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
Click to expand...
Click to collapse
Just noticed, you're entering the command wrong. The only space in this command is between the 't' and the '-' fastboot --set-active=b
You need to check out the _b slot, see what is on it and whether it will boot or not. If it does boot, check the settings and take note of everything. If it doesn't boot then we'll go from there. Just copy the fastboot command as I typed it.

Recovering soft brick G5

Hi just on the off chance anyone see's this and can advise.
Family updated their G5 with OTA security update. OTA screwed the device (soft-brick can still access recovery and adb via pc), they reckon it's out of warranty so not worth taking in.
I'm following : https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897 to try to reinstate stock rom and revive the device. However, a little concerned that as the device is not user development mode enabled that i may hit hurdles (e.g. hard brick the bugger).
oem is marked as locked and i have a "fastboot flash mode (secure)" warning in bootloader. Is this going to mess with my plans?
Device is XT1675 (retail) which i understand is out of OTA so little confused as to why the initial error but am certain owner has not tampered in any way with the device. Before you ask, Motorola's solution was 'pay a repair guy'.

UPDATE:
Unsurprisingly, the instrs didn't work and i hit a hurdle. flashing boot resulted in an error "validation failed". Seems the error thinks that i'm trying to flash an old version... There doesn't appear to be a more recent G5 rom available so am i screwed?

deedb said:
Hi just on the off chance anyone see's this and can advise.
Family updated their G5 with OTA security update. OTA screwed the device (soft-brick can still access recovery and adb via pc), they reckon it's out of warranty so not worth taking in.
I'm following : https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897 to try to reinstate stock rom and revive the device. However, a little concerned that as the device is not user development mode enabled that i may hit hurdles (e.g. hard brick the bugger).
oem is marked as locked and i have a "fastboot flash mode (secure)" warning in bootloader. Is this going to mess with my plans?
Device is XT1675 (retail) which i understand is out of OTA so little confused as to why the initial error but am certain owner has not tampered in any way with the device. Before you ask, Motorola's solution was 'pay a repair guy'.
Click to expand...
Click to collapse
Run the "fastboot getvar all" command and paste the whole output into your reply (delete lines with a personal data such as IMEI and serial number first). According to it, I should be able to send you a link for a fastboot firmware that won't hardbrick your device (hardbrick occurs if older gpt and/or bootloader is flashed).
Btw, you can find the bootloader status (unlocked or not) in the bootloader menu. "Flashing unlocked" means it's unlocked, "oem_locked" means it isn't. However, it shouldn't matter as long as you flash the digitally signed stock firmware of the same or newer version (flashing an older one will immediately hardbrick your device, as I already wrote).

deedb said:
UPDATE:
Unsurprisingly, the instrs didn't work and i hit a hurdle. flashing boot resulted in an error "validation failed". Seems the error thinks that i'm trying to flash an old version... There doesn't appear to be a more recent G5 rom available so am i screwed?
Click to expand...
Click to collapse
Use lenovo Moto smart assistant app in pc and select recovery mode and it will flash the whole firmware.

Andrej_SK said:
Run the "fastboot getvar all" command and paste the whole output into your reply (delete lines with a personal data such as IMEI and serial number first). According to it, I should be able to send you a link for a fastboot firmware that won't hardbrick your device (hardbrick occurs if older gpt and/or bootloader is flashed).
Btw, you can find the bootloader status (unlocked or not) in the bootloader menu. "Flashing unlocked" means it's unlocked, "oem_locked" means it isn't. However, it shouldn't matter as long as you flash the digitally signed stock firmware of the same or newer version (flashing an older one will immediately hardbrick your device, as I already wrote).
Click to expand...
Click to collapse
Thanks for your reply and sorry for being so tardy with mine. bootloader is definitely locked "oem_locked".
getvar results as follows;
(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=A5 FV=000000000
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=
(bootloader) cpu: MSM8937
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) date: 07-09-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 6 22:37: 2 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.
(bootloader) ro.build.fingerprint[1]: 8.85-13-2/d04a4:user/rele
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.ce
(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_22.29.02.69R CEDRIC_EMEA_C
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g339
(bootloader) kernel.version[1]: [email protected]) (gcc version 4
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Oct 9 13:5
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=26cc248
(bootloader) devcfg.git: git=26cc248
(bootloader) keymaster.git: git=26cc248
(bootloader) cmnlib.git: git=26cc248
(bootloader) cmnlib64.git: git=26cc248
(bootloader) prov.git: git=26cc248
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retgb
(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

deedb said:
Thanks for your reply and sorry for being so tardy with mine. bootloader is definitely locked "oem_locked".
getvar results as follows;
(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=A5 FV=000000000
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=
(bootloader) cpu: MSM8937
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) date: 07-09-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 6 22:37: 2 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.
(bootloader) ro.build.fingerprint[1]: 8.85-13-2/d04a4:user/rele
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.ce
(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_22.29.02.69R CEDRIC_EMEA_C
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g339
(bootloader) kernel.version[1]: [email protected]) (gcc version 4
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Oct 9 13:5
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=26cc248
(bootloader) devcfg.git: git=26cc248
(bootloader) keymaster.git: git=26cc248
(bootloader) cmnlib.git: git=26cc248
(bootloader) cmnlib64.git: git=26cc248
(bootloader) prov.git: git=26cc248
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retgb
(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
Click to expand...
Click to collapse
Open this site https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/, download the firmware with "OPPS28.85-13-2" in the filename, extract the full content of the downloaded zip into the folder where's your adb/fastboot installed and flash it using the commands below. You can download the "OPPS28.85-13-4" firmware also, but "OPPS28.85-13-2" will be just enough to do not brick your phone (difference: 13-4 is firmware with december 2018 security patch while 13-2 is firmware with october 2018 security patch).
Commands to flash (data in the internal storage will be wiped):
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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

Hello, can someone help me find a firmware that will remove the brick in my xt1671? My Getvar all result is:
(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: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: 2c35acf3
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: C0F87BA300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(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: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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.063s
Thank you!

Maylo0292 said:
Hello, can someone help me find a firmware that will remove the brick in my xt1671? My Getvar all result is:
(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: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: 2c35acf3
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: C0F87BA300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(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: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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.063s
Thank you!
Click to expand...
Click to collapse
There are some important lines such as "(bootloader)ro.build.fingerprint[0]" and "(bootloader)ro.build.fingerprint[1]" missing. It seems that your device was previously hardbricked and now, it is booted (into the fastboot) using the sdcard only, isn't it?

Maylo0292 said:
Hello, can someone help me find a firmware that will remove the brick in my xt1671? My Getvar all result is:
(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: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: 2c35acf3
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: C0F87BA300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(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: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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.063s
Thank you!
Click to expand...
Click to collapse
Here you can get the firmware. https://mirrors.lolinet.com/firmware/moto/cedric/official/
And remove serial no from getvar.

Andrej_SK said:
There are some important lines such as "(bootloader)ro.build.fingerprint[0]" and "(bootloader)ro.build.fingerprint[1]" missing. It seems that your device was previously hardbricked and now, it is booted (into the fastboot) using the sdcard only, isn't it?
Click to expand...
Click to collapse
Thanks for answering. Just turn on fastboot even without the SD Card, when trying to flash any firmware gives errors because the bootloader locked. Any suggestions?
---------- Post added at 06:19 PM ---------- Previous post was at 06:10 PM ----------

Maylo0292 said:
Thanks for answering. Just turn on fastboot even without the SD Card, when trying to flash any firmware gives errors because the bootloader locked. Any suggestions?
Click to expand...
Click to collapse
It doesn't matter that your bootloader is locked - you're flashing official firmware images via fastboot - that's what they are designed for
You are more likely flashing incorrect firmware or firmware that is too old
Without the error output who knows

TheFixItMan said:
It doesn't matter that your bootloader is locked - you're flashing official firmware images via fastboot - that's what they are designed for
You are more likely flashing incorrect firmware or firmware that is too old
Without the error output who knows
Click to expand...
Click to collapse
I have tried to install the latest firmware version from the RETAIL and several companies and I always get the following result in fastboot:
C:\Users\Escritorio\Downloads\Firmware>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.061s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.172s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 5.047s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 5.291s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 2.173s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 2.215s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 16.292s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.495s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 15.957s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.179s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash dsp adspso.bin
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 15.551s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 15.579s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [141.870s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 141.946s

Maylo0292 said:
I have tried to install the latest firmware version from the RETAIL and several companies and I always get the following result in fastboot:
C:\Users\Escritorio\Downloads\Firmware>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.061s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.172s
...
Click to expand...
Click to collapse
That's why does it fail. You are trying to flash older firmware.
Try to flash this one https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (clicking the link will start the download. Source here https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/).

Maylo0292 said:
(bootloader) Security version downgrade
Click to expand...
Click to collapse
What the above post says - this error means the firmware you are trying to flash is too old
gpt and bootloader must be the same or newer than what is already on your device

Andrej_SK said:
That's why does it fail. You are trying to flash older firmware.
Try to flash this one https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (clicking the link will start the download. Source here https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/).
Click to expand...
Click to collapse
Thank you very much for answering. It's just the firmware that I downloaded and installed and which gives me that error that I mentioned. Do you know where I can get the most current?
---------- Post added at 11:15 PM ---------- Previous post was at 11:09 PM ----------
TheFixItMan said:
What the above post says - this error means the firmware you are trying to flash is too old
gpt and bootloader must be the same or newer than what is already on your device
Click to expand...
Click to collapse
Thank you very much for answering.
It's strange for me to get that error, I downloaded and installed the firmware CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Do you know which one I should install to fix it?

Maylo0292 said:
Thank you very much for answering.
It's strange for me to get that error, I downloaded and installed the firmware CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Do you know which one I should install to fix it?
Click to expand...
Click to collapse
I don't own this device
I suggest you download the most recent for your region
Eg
Retin = India
Retgb = United Kingdom
Reteu = Europe
You get the idea
Obviously if you flashed an ota from a different region you may have to use firmware from that region as it maybe newer than yours which is why you should never flash otas outside of the about phone section of your phone unless they come direct from the manufacturer and not via a 3rd party website

Maylo0292 said:
Thank you very much for answering. It's just the firmware that I downloaded and installed and which gives me that error that I mentioned. Do you know where I can get the most current?
---------- Post added at 11:15 PM ---------- Previous post was at 11:09 PM ----------
Thank you very much for answering.
It's strange for me to get that error, I downloaded and installed the firmware CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Do you know which one I should install to fix it?
Click to expand...
Click to collapse
That's weird, as you are always getting security downgrade error, but OPPS28.85-16-6 is the latest available official build for Moto G5 ever released by Lenovo (https://support.motorola.com/in/en/softwareupgrade). Are you sure that you are trying to flash the correct firmware?

Andrej_SK said:
That's weird, as you are always getting security downgrade error, but OPPS28.85-16-6 is the latest available official build for Moto G5 ever released by Lenovo (https://support.motorola.com/in/en/softwareupgrade). Are you sure that you are trying to flash the correct firmware?
Click to expand...
Click to collapse
I reinstalled the firmware PPS28.85-16-6 and it no longer gives the downgrade error but now the following comes out in the fastboot:
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.003s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.065s
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.197s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.409s
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.628s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.800s
Do you know why this is?
---------- Post added at 06:55 PM ---------- Previous post was at 06:51 PM ----------
TheFixItMan said:
I don't own this device
I suggest you download the most recent for your region
Eg
Retin = India
Retgb = United Kingdom
Reteu = Europe
You get the idea
Obviously if you flashed an ota from a different region you may have to use firmware from that region as it maybe newer than yours which is why you should never flash otas outside of the about phone section of your phone unless they come direct from the manufacturer and not via a 3rd party website
Click to expand...
Click to collapse
Thank you. I went back to flashing the firmware PPS28.85-16-6 that you suggested to me and now it gives the following in fastboot:
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.003s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.065s
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.197s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.409s
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.628s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.800s
Do you know why this is?

Did you start the flashing process with
fastboot oem fb_mode_set
Then
fastboot flash gpt
fastboot flash bootloader
And so on
If so then probably same issue
If you have an sd card with the mmcblk0 image on it then you can test your device is working correctly
Flash everything from the latest firmware except gpt & bootloader
Restart the phone back to bootloader with the sd card in
Use volume keys to select the start normally option
Your phone should boot
If you want to boot the phone without the SD card you need to find firmware which will allow gpt and bootloader to flash

TheFixItMan said:
Did you start the flashing process with
fastboot oem fb_mode_set
Then
fastboot flash gpt
fastboot flash bootloader
And so on
If so then probably same issue
If you have an sd card with the mmcblk0 image on it then you can test your device is working correctly
Flash everything from the latest firmware except gpt & bootloader
Restart the phone back to bootloader with the sd card in
Use volume keys to select the start normally option
Your phone should boot
If you want to boot the phone without the SD card you need to find firmware which will allow gpt and bootloader to flash
Click to expand...
Click to collapse
I started flashing with those commands but I get the same results, I think it's a serious problem in the EMMC so I'll take it to support. Thank you very much for the help.

Moto Z2 Force T-Mobile branding -> flash to retail firmware won't work

Hi there,
I'm new to xda. Thanks for having me.
I am new to the whole topic of unlocking/flashing a mobile phone, since I did not see a real need for it until now.
What's the story:
I bought a new Motorola Moto Z2 Force (XT1789-04) on eBay. The phone was shipped from the US apparently (I live in Germany).
It has a T-Mobile branding pre-installed, which was not mentioned before and which I find terrible.
So I decided to flash the Z2 with a retail firmware to get rid of all those useless pre-installed apps.
I started reading a bit about how to do this. The first pages suggested to use RSD Lite with the latest motorola drivers and provided appropriate stock firmware.
I went into developers options on the phone, and allowed USB debugging. I started fastboot with "volume down" and power.
However, the phone is not recognized in RSD Lite. The list remains empty. I reinstalled the motorola driver multiple times, rebooting my Win10 PC as was suggested.
I also tried the universal ADB drivers. No change.
I then used the adb / fastboot cmd lines to check if something is amiss. And i found a couple of strange things:
Code:
fastboot getdev all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
[B](bootloader) secure: no[/B]
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: [XXXXXXXXXXX]
(bootloader) [B]cid: 0xDEAD[/B]
(bootloader) channelid: 0x00
(bootloader) uid: D7BF5C89
(bootloader) [B]securestate: engineering[/B]
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [XXXXXXXXXXX]
(bootloader) meid:
(bootloader) date: 01-23-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4272
(bootloader) iccid: 89148000003630606544
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08R NNS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:pmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:prov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.119s
I am unable to get unlock data.
Code:
fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
finished. total time: 0.003s
Code:
fastboot flashing get_unlock_ability
...
(bootloader) use get_unlock_bootloader_nonce and web portal
(bootloader) .....motorola.com/unlockbootloader
OKAY [ 0.004s]
finished. total time: 0.005s
In the phone setup I also noticed, that "unlock bootloader" is greyed out. It states, the bootloader would already be unlocked.
Now I tried the unlock cmd in fastboot, since it should state something like already unlocked, but instead I get this message:
Code:
fastboot oem unlock
...
(bootloader) Unsupported on engineering phone
OKAY [ 0.001s]
finished. total time: 0.002s
Now I found this quite confusing, but I tried to flash TWRP, in case this might resolve the problems with "engineering mode" without quite knowing what that really implies.
I downloaded the latest TWRP for nash (Z2 Force) and tried to flash it over fastboot:
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (34224 KB)...
OKAY [ 0.081s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.085s
Now I am out of ideas.
Can anyone help me? Maybe start by explaining, why my phone doesn't just let me do the things I want...
Thanks!

12die4 said:
Hi there,
I'm new to xda. Thanks for having me.
I am new to the whole topic of unlocking/flashing a mobile phone, since I did not see a real need for it until now.
What's the story:
I bought a new Motorola Moto Z2 Force (XT1789-04) on eBay. The phone was shipped from the US apparently (I live in Germany).
It has a T-Mobile branding pre-installed, which was not mentioned before and which I find terrible.
So I decided to flash the Z2 with a retail firmware to get rid of all those useless pre-installed apps.
I started reading a bit about how to do this. The first pages suggested to use RSD Lite with the latest motorola drivers and provided appropriate stock firmware.
I went into developers options on the phone, and allowed USB debugging. I started fastboot with "volume down" and power.
However, the phone is not recognized in RSD Lite. The list remains empty. I reinstalled the motorola driver multiple times, rebooting my Win10 PC as was suggested.
I also tried the universal ADB drivers. No change.
I then used the adb / fastboot cmd lines to check if something is amiss. And i found a couple of strange things:
Code:
fastboot getdev all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
[B](bootloader) secure: no[/B]
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: [XXXXXXXXXXX]
(bootloader) [B]cid: 0xDEAD[/B]
(bootloader) channelid: 0x00
(bootloader) uid: D7BF5C89
(bootloader) [B]securestate: engineering[/B]
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [XXXXXXXXXXX]
(bootloader) meid:
(bootloader) date: 01-23-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4272
(bootloader) iccid: 89148000003630606544
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08R NNS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:pmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:prov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.119s
I am unable to get unlock data.
Code:
fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
finished. total time: 0.003s
Code:
fastboot flashing get_unlock_ability
...
(bootloader) use get_unlock_bootloader_nonce and web portal
(bootloader) .....motorola.com/unlockbootloader
OKAY [ 0.004s]
finished. total time: 0.005s
In the phone setup I also noticed, that "unlock bootloader" is greyed out. It states, the bootloader would already be unlocked.
Now I tried the unlock cmd in fastboot, since it should state something like already unlocked, but instead I get this message:
Code:
fastboot oem unlock
...
(bootloader) Unsupported on engineering phone
OKAY [ 0.001s]
finished. total time: 0.002s
Now I found this quite confusing, but I tried to flash TWRP, in case this might resolve the problems with "engineering mode" without quite knowing what that really implies.
I downloaded the latest TWRP for nash (Z2 Force) and tried to flash it over fastboot:
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (34224 KB)...
OKAY [ 0.081s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.085s
Now I am out of ideas.
Can anyone help me? Maybe start by explaining, why my phone doesn't just let me do the things I want...
Thanks!
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi, the command reply is seen in the first code box.
Sorry, I mixed up the headlines. It's NOT "fastboot getdev all", but as you said "fastboot getvar all". My mistake. :cyclops:

12die4 said:
Hi, the command reply is seen in the first code box.
Sorry, I mixed up the headlines. It's NOT "fastboot getdev all", but as you said "fastboot getvar all". My mistake. :cyclops:
Click to expand...
Click to collapse
Does the device still boot normally?
Sent from my Moto E (4) using Tapatalk

Looks like you have an engineering phone, bootloader should already be unlocked. I haven't had any experience with an engineering phone so I don't know the limitations... if any.
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)

41rw4lk said:
Looks like you have an engineering phone, bootloader should already be unlocked. I haven't had any experience with an engineering phone so I don't know the limitations... if any.
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)
Click to expand...
Click to collapse
Correct getvar says securestate engineering
Sent from my perry_f using XDA Labs
---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------
If you get twrp installed, make a complete backup.
Engineering devices have unique firmware, I think.
It may not behave like a consumer model.
Sent from my perry_f using XDA Labs

41rw4lk said:
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)
Click to expand...
Click to collapse
Thank! I will try to do that. I understand that you can Boot a remote (PC located) Boot Image with this command? Flashing TWRP via fastboot didn't however. Not sure why.

41rw4lk said:
Looks like you have an engineering phone, bootloader should already be unlocked. I haven't had any experience with an engineering phone so I don't know the limitations... if any.
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)
Click to expand...
Click to collapse
Great, fastboot boot twrp.img worked!
What do I do now? My idea was: Run "install" and try to flash the new Firmware via TWRP.
Therefore I need to copy the new img-file onto an sd-card and select it in TWRP as source. Right?
Or which procedure would you recommend?
sd_shadow said:
[/COLOR]If you get twrp installed, make a complete backup.
Engineering devices have unique firmware, I think.
It may not behave like a consumer model.
Click to expand...
Click to collapse
Thanks for the advice. I tried a backup with all boxes checked - there was a failure (error 255).
But when checking only firmware and bootloader, the backup worked fine.
Do I need the other options or are firmware and bootloader sufficient for my purposes? I'm not sure, what is actually overwritten when installing the stock firmware.

12die4 said:
Great, fastboot boot twrp.img worked!
What do I do now? My idea was: Run "install" and try to flash the new Firmware via TWRP.
Therefore I need to copy the new img-file onto an sd-card and select it in TWRP as source. Right?
Or which procedure would you recommend?
Thanks for the advice. I tried a backup with all boxes checked - there was a failure (error 255).
But when checking only firmware and bootloader, the backup worked fine.
Do I need the other options or are firmware and bootloader sufficient for my purposes? I'm not sure, what is actually overwritten when installing the stock firmware.
Click to expand...
Click to collapse
You want boot twrp, install twrp in booted twrp with a twrp.zip, then back up.
Sent from my ali using XDA Labs
---------- Post added at 05:02 AM ---------- Previous post was at 04:57 AM ----------
https://dl.twrp.me/nash/
Sent from my ali using XDA Labs

sd_shadow said:
You want boot twrp, install twrp in booted twrp with a twrp.zip, then back up.
Sent from my ali using XDA Labs
---------- Post added at 05:02 AM ---------- Previous post was at 04:57 AM ----------
https://dl.twrp.me/nash/
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hurra! Installing twrp worked now. Thanks!
How do I get to boot twrp now that it is installed locally? Do I still need to use the command "fastboot boot twrp.img" or is there a possibility without adb/fastboot protocol?
I was also able to create a backup of all partitions. I only deselected "Data (excl. storage)" in the options, since the phone was not actively used yet, so there shouldn't be any data that's relevant for backup.
Next I tried installing the new retail firmware ("NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"), but TWRP states the ZIP has an invalid file format.
Why is it not working? Is it an incorrect firmware after all?

12die4 said:
Hurra! Installing twrp worked now. Thanks!
How do I get to boot twrp now that it is installed locally? Do I still need to use the command "fastboot boot twrp.img" or is there a possibility without adb/fastboot protocol?
I was also able to create a backup of all partitions. I only deselected "Data (excl. storage)" in the options, since the phone was not actively used yet, so there shouldn't be any data that's relevant for backup.
Next I tried installing the new retail firmware ("NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"), but TWRP states the ZIP has an invalid file format.
Why is it not working? Is it an incorrect firmware after all?
Click to expand...
Click to collapse
You should be able to boot to twrp using bootloader recovery option.
Stock firmware is not twrp compatible.
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
You should be able to boot to twrp using bootloader recovery option.
Stock firmware is not twrp compatible.
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Ow, that sounds tricky. (tools that are no longer updated and might or might not work...)
For now, I tried to install LineageOS 17.1 on my Z2 Force.
Maybe there is no need to keep Retail Moto-Firmware after all...
However I have some issues with LineageOS. I will post them in the corresponding thread.
For now. Thanks a lot!

XT1922-2 JETER softbricked (newbie)

Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.

Here's all the variables if that's helpful:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-aljeter_retail-b1f322d35c1-2
(bootloader) version-bootloader[1]: 00404
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZL4223V3D5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 3572CA9F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 08-29-2018
(bootloader) sku: XT1922-2
(bootloader) carrier_sku: XT1922-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 5 11:34:57 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter_n/aljeter_n:9/PPP
(bootloader) ro.build.fingerprint[1]: S29.55-35-18-7/6a0d0:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.7.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: M8937_34.42.05.98R JETER_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g3e480e17e11
(bootloader) kernel.version[1]: f-04280-g407726838ebf ([email protected]
(bootloader) kernel.version[2]: 8) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Sat Apr 4 12:
(bootloader) kernel.version[4]: 24:37 CDT 2020
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-0d2031d6b9-200404
(bootloader) rpm.git: MBM-2.1-aljeter_retail-af31f6ae-200404
(bootloader) tz.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) prov.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) aboot.git: MBM-2.1-aljeter_retail-b1f322d35c1-200404
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: eegb
(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.152s
Click to expand...
Click to collapse

xt123xt said:
Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.
Click to expand...
Click to collapse
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Ruben8ap said:
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
Click to expand...
Click to collapse
Thank you for your reply.
It gave me an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system aljeter.zip
target reported max download size of 535822336 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 411641469 is not a multiple of the block size 4096
sending sparse 'system' 1/3 (523260 KB)...
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
OKAY [ 17.139s]
writing 'system' 1/3...
(bootloader) Invalid sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.145s
Click to expand...
Click to collapse

Try these https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETEU/

I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.

xt123xt said:
I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.
Click to expand...
Click to collapse
Download this file --> https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Then you open the CMD and put in fastboot devices and the phone code should appear, of course the phone should already be in fastboot mode for that moment.
If everything is in order you should copy these commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Just select all then copy and paste them into the CMD and the stock installation process will start :fingers-crossed:

I suppose you've saved my phone. Thank you very much!

Hi, I carried out the instruction as given above by Ruben8ap, on my XT1922-2 Aljeter Moto G6 Play phone, and have recovered my phone, so I can boot into the OS, but I have lost access to Fastboot and TWRP, etc. So, I now have a phone that is stuck with this OS and no way of gaining root access or anything else. My bootloader says AP Fastboot Flash Mode (Secure). I cannot flash anything from the stock recovery on the SD card. Can anyone advise how I can get out of this state?

Question Moto G60 not starting & Flashing Locked

Hello Guys,
I have Moto G60. I have unlocked boot loader and downgrade with Stock Android 11 and Locked boot loader again.
After flashing locked, when I started my phone, it shows me error "No Valid Operating System could be Found. The device will not boot."
I have tried Lenovo RSA tool to rescue my phone but it gets failed, same in RSD Lite.
Now, I am trying to unlock boot loader again using ADB tools and it gives me error that "Check 'OEM unlocking' in Android Settings > Developer"
Can anyone help me?
Thanks in advance.
Milan

milan.vyas7 said:
Hello Guys,
I have Moto G60. I have unlocked boot loader and downgrade with Stock Android 11 and Locked boot loader again.
After flashing locked, when I started my phone, it shows me error "No Valid Operating System could be Found. The device will not boot."
I have tried Lenovo RSA tool to rescue my phone but it gets failed, same in RSD Lite.
Now, I am trying to unlock boot loader again using ADB tools and it gives me error that "Check 'OEM unlocking' in Android Settings > Developer"
Can anyone help me?
Thanks in advance.
Milan
Click to expand...
Click to collapse
Did you boot the phone to make sure everything's ok before locking the bootloader?
I see a lot of people with this issue. Locking the bootloader should be the absolute last step you do. After you make sure everything works fine.
The problem is you don't have USB debugging on anymore, so no adb. Bootloader is locked, and you've got no access to the OS, so you can't either enable or disable OEM unlocking.
I'll look around to see if there's any way to fix this at home. But I'm afraid the only way might be to bring the phone to a repair center.

arsradu said:
Did you boot the phone to make sure everything's ok before locking the bootloader?
I see a lot of people with this issue. Locking the bootloader should be the absolute last step you do. After you make sure everything works fine.
The problem is you don't have USB debugging on anymore, so no adb. Bootloader is locked, and you've got no access to the OS, so you can't either enable or disable OEM unlocking.
I'll look around to see if there's any way to fix this at home. But I'm afraid the only way might be to bring the phone to a repair center.
Click to expand...
Click to collapse
Yes, when I have unlocked bootloader and downgrade from Android 12 to Android 11 and every thing was working perfectly.
To, install banking apps on my mobile, I thought it will be good to relock the bootloader.
Once I locked the bootloader and reboot my phone, I get this error.
I have also bring my phone to mobile shops to get it repaired but no luck.

milan.vyas7 said:
Yes, when I have unlocked bootloader and downgrade from Android 12 to Android 11 and every thing was working perfectly.
To, install banking apps on my mobile, I thought it will be good to relock the bootloader.
Once I locked the bootloader and reboot my phone, I get this error.
I have also bring my phone to mobile shops to get it repaired but no luck.
Click to expand...
Click to collapse
For banking apps to work, you only need the device to be non-rooted. Bootloader status doesn't matter, for as far as I know. But I guess it depends on the app.
Anyway, I'm guessing OEM unlocking was not checked before you locked the bootloader, right? Otherwise it shouldn't have complained about it when you tried to unlock again.
Weird thing. I don't know where you got the bootloader unlocking procedure, but on the official Motorola site that I used to unlock the bootloader, it said to use:
fastboot oem unlock [UNLOCK_CODE]
But Google's documentation mentioned something about newer devices using "fastboot flashing" command. Kinda confusing...
They're probably the same. But I never used this command. Also, when you try to unlock using "fastboot flashing" don't you also need to provide the unlock code...?
I don't know man... I don't know what to say. I was thinking of going back to stock Android 12 just to test this theory, but now I'm not so sure. )
I have unlocked and locked bootloader before, on other Motorola phones. Successfully of course. ) So...I'm not sure why so many people keep getting into this issue.
By the way, what is the exact error you get with RSA when trying to restore your device? That should have worked...even with a locked bootloader. After all, it asumes the bootloader is locked. Can you boot into fastboot mode? Is the device recognised in fastboot mode?
I remember I had a failure with RSA one time, but just restarting the process made it go away, and flashing finished successfully.
Anyway, to check fastboot status, while in fastboot mode, do the following command:
fastboot devices
It should display your device underneath. After that, you can go restore your device with RSA.

arsradu said:
For banking apps to work, you only need the device to be non-rooted. Bootloader status doesn't matter, for as far as I know. But I guess it depends on the app.
Anyway, I'm guessing OEM unlocking was not checked before you locked the bootloader, right? Otherwise it shouldn't have complained about it when you tried to unlock again.
Weird thing. I don't know where you got the bootloader unlocking procedure, but on the official Motorola site that I used to unlock the bootloader, it said to use:
fastboot oem unlock [UNLOCK_CODE]
But Google's documentation mentioned something about newer devices using "fastboot flashing" command. Kinda confusing...
They're probably the same. But I never used this command. Also, when you try to unlock using "fastboot flashing" don't you also need to provide the unlock code...?
I don't know man... I don't know what to say. I was thinking of going back to stock Android 12 just to test this theory, but now I'm not so sure. )
I have unlocked and locked bootloader before, on other Motorola phones. Successfully of course. ) So...I'm not sure why so many people keep getting into this issue.
By the way, what is the exact error you get with RSA when trying to restore your device? That should have worked...even with a locked bootloader. After all, it asumes the bootloader is locked. Can you boot into fastboot mode? Is the device recognised in fastboot mode?
I remember I had a failure with RSA one time, but just restarting the process made it go away, and flashing finished successfully.
Anyway, to check fastboot status, while in fastboot mode, do the following command:
fastboot devices
It should display your device underneath. After that, you can go restore your device with RSA.
Click to expand...
Click to collapse
Hi,
Please find attached screenshot of error in RSA.
In fastboot mode its showing me device while running command: "fastboot devices"

Yeah, looks like there are a lot of Motorola users with this exact issue.
So, the problem here is that, when you flash the ROM with bootloader unlocked, OEM Unlocking is in the Off position, and greyed out. Showing "bootloader is already unlocked". So you can't change that.
Then you try to relock the bootloader, data gets erased, and you can't boot. No idea why it's showing "no valid operating system could be found". That's the first problem.
Also, when you try to unlock again, it complains about the OEM Unlocking switch not being ON, which...well, you couldn't turn on to begin with, cause it was inactive/greyed out, saying bootloader is already unlocked (which it was).
What's interesting is that, according to Google, that option should be persistent to factory resets. I guess it's persistent to user triggered factory resets, but not when bootloader is being locked and triggers the erase userdata on its own. Which I guess makes sense. But with the OS not booting, that option being likely unchecked...it's becoming a huge pain in the butt.
Some people said to wait 7 days and then try to reflash using RSA.
In the meantime, I've found an awesome guide here.
And some technical details from google here.
Also this about boot flow.
I've reverted to stock Android 12 myself, for the time being. But I did not lock the bootloader. For multiple reasons. This being only one of them. And I'm not planning to, until I find out more about this issue.
I'll let you know if I find anything more.
Update:
Ok, so apparently the switch being in the off position doesn't really have any effect on the software functionality after relocking the bootloader. You CAN relock the bootloader, even with the switch greyed out and in the OFF position. It should be ok, as long as you don't try to lock the bootloader on a custom ROM.
So, my advice would be using LMSA to flash the stock ROM, make sure it boots, lock the bootloader, and without rebooting the system, go into recovery and do a wipe data/factory reset. Then reboot to system.
It worked fine for me. Already did this operation twice. All good. Just make sure everything is clean (LMSA should take care of this).

You can boot into bootloader, right?
If so, can you try these commands?
fastboot getvar current-slot
Should return something like this:
current-slot: a
or
current-slot: b
If it says current-slot: a, try to switch to b slot with this command:
fastboot --set-active=b
If your current slot is b, try to change it to slot a with the following command:
fastboot --set-active=a
Then try to reboot.
If you're on Windows, do NOT use Minimal ADB and fastboot. Use this instead: https://developer.android.com/studio/releases/platform-tools
Let me know if you still encounter that issue.

Also, another question: did you flash a custom recovery? Cause you might have needed to flash back stock recovery (boot.img) before locking the bootloader.
What happened here I think is that you locked the bootloader. But slot a and slot b might have different recoveries.
For testing, I reverted to stock Android 11 on my Moto One Action. And I've noticed, on slot b, I had Pixel Experience recovery. So I flashed stock first.
Then booted from slot a, and the OEM Unlocking switch was still greyed out but on the ON position (bootloader allowed to be unlocked). Still with the same message "bootloader is already unlocked", but switch set to ON. Which is a big difference.
Then I locked the bootloader. And with fingers crossed, successfully booted into the OS.
And when I booted back, OEM Unlocking was no longer inactive. And it can be set to ON or OFF, just like in the beginning.
So, I think the goal here would be to get that switch greyed out and in the ON position. I think that's a good sign.
After that, locking the bootloader should work just fine.
In your case, I think it's trying to boot from an inactive slot. Or one that doesn't have an operating system linked to it. The error you get seems accurate for this case (no valid operating system found). So of course it cannot boot. So we just need to figure out why there's no valid operating system found.
But I'm waiting for more info, before reaching a conclusion. Anyway, I've learned a lot about these things in the past couple of days.
Also, another thing I've learned is that you can't have Google Pay (now called Wallet) and Tap to Pay working on stock ROM if your bootloader is unlocked. It's not gonna pass the CTS match test. So...in order to get that, either you're on a custom ROM, obviously with bootloader unlocked, or on a stock ROM, rooted, with Magisk and certain tricks to make it work. Which..,since you're on stock ROM, I'm guessing you don't want root. So...yeah.

Also, please, run this command from Fastboot mode:
Code:
fastboot getvar all
and post the output here.
You can remove IMEIs and other personal data. We don't need those.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-hanoip_retail-aea4f158e7-210611
(bootloader) product: hanoip
(bootloader) board: hanoip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM2V8001CM-B707 FV=1500 WB=0
(bootloader) ram: 6GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ZY22F4X32L
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 290C2617
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3
(bootloader) imei2: 3
(bootloader) meid:
(bootloader) date: 01-18-2022
(bootloader) sku: XT2135-2
(bootloader) carrier_sku: XT2135-2
(bootloader) battid: SB18D01687
(bootloader) battery-voltage: 4316
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: reteu
(bootloader) ro.build.fingerprint[0]: motorola/hanoip_retailenq/hanoip:1
(bootloader) ro.build.fingerprint[1]: 1/RRIS31.Q1-42-51-12-4/24f96:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-07700-SMxxx0.0
(bootloader) version-baseband[0]: M7150_09.297.01.75.01R HANOIP_EUAPEMDS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.190-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Mon M
(bootloader) kernel.version[4]: ay 2 07:50:18 CDT 2022
(bootloader) git:xbl: MBM-3.0-hanoip_retail-e90680732-210611
(bootloader) git:xbl_config: MBM-3.0-hanoip_retail-e90680732-210611
(bootloader) git:aop: MBM-3.0-hanoip_retail-4bfd5e5-210611
(bootloader) git:tz: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:hyp: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:devcfg: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:cmnlib: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:keymaster: MBM-3.0-hanoip_retail-bf902af-210611
(bootloader) git:storsec: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) gitrov: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:abl: MBM-3.0-hanoip_retail-aea4f158e7-210611
(bootloader) git:qupfw: MBM-3.0-hanoip_retail-6ac31cc-210611
(bootloader) git:uefisecapp: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) frp-state: protected (77)
(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: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D03127
(bootloader) primary-display: tm_ili7807s_fhd_vid
(bootloader) secondary-display:
all: listed above
finished. total time: 0.178s

milan.vyas7 said:
Hello Guys,
I have Moto G60. I have unlocked boot loader and downgrade with Stock Android 11 and Locked boot loader again.
After flashing locked, when I started my phone, it shows me error "No Valid Operating System could be Found. The device will not boot."
I have tried Lenovo RSA tool to rescue my phone but it gets failed, same in RSD Lite.
Now, I am trying to unlock boot loader again using ADB tools and it gives me error that "Check 'OEM unlocking' in Android Settings > Developer"
Can anyone help me?
Thanks in advance.
Milan
Click to expand...
Click to collapse
Good morning, dear friend, I also had the same error and I regret to inform you that there is no resolution without using certain equipment at the moment, the only possible way to solve this problem at the moment would be through a JTAG BOX type MEDUSA PRO 2 or OCTOPLUS, I'll explain why, recently with the update to android 12, a security patch also came with it, with the same problem, it turns out that the boot structures that are with android 11, are not compatible with the 12 and it ends up that you can't go back, this error seems intentional, the only way to be solving it even because the bootloader is blocked would be you using a box to rewrite the system in the device's UFS memories directly through the JTAG which is the direct connection from the box with the motherboard of the device, another solution would be to send it to motorola itself, which according to them it is necessary to change the entire motherboard of the device and the concert costs around 181.71 Dollar, if you are lucky and find a technician in your city who operates with jtag, the concert costs around 40 Dollars, I'm Brazilian so for me, the plate replacement came with a budget of R$ 920.00 and the concert for JTAG R$ 200.00
A hug in advance and if you need to just call.

arsradu said:
Also, please, run this command from Fastboot mode:
Code:
fastboot getvar all
and post the output here.
You can remove IMEIs and other personal data. We don't need those.
Click to expand...
Click to collapse
Hello Arsradu,
I have gone through steps which you given me to run on platform tools and output is as below.
C:\platform-tools_r33.0.3-windows\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.004s
C:\platform-tools_r33.0.3-windows\platform-tools>fastboot --set-active=b
Setting current slot to 'b' FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools_r33.0.3-windows\platform-tools>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-hanoip_retail-aea4f158e7-210611
(bootloader) product: hanoip
(bootloader) board: hanoip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB MICRON MT128GASAO4U21 FV=0106 WB=0
(bootloader) ram: 6GB MICRON LP4 DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ********
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E7F4957D
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: ************
(bootloader) imei2: *******
(bootloader) meid:
(bootloader) date: 04-15-2021
(bootloader) sku: XT2135-2
(bootloader) carrier_sku: XT2135-2
(bootloader) battid: SB18C87844
(bootloader) battery-voltage: 3947
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retin
(bootloader) ro.build.fingerprint[0]: motorola/hanoip_retailnq/hanoip:11
(bootloader) ro.build.fingerprint[1]: /RRI31.Q1-42-42-3/149b5:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-07700-SMxxx0.0
(bootloader) version-baseband[0]: M7150_09.297.01.60R HANOIP_EUAPEMDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.14.190-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Fri J
(bootloader) kernel.version[4]: un 11 07:59:53 CDT 2021
(bootloader) git:xbl: MBM-3.0-hanoip_retail-e90680732-210611
(bootloader) git:xbl_config: MBM-3.0-hanoip_retail-e90680732-210611
(bootloader) git:aop: MBM-3.0-hanoip_retail-4bfd5e5-210611
(bootloader) git:tz: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:hyp: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:devcfg: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:cmnlib: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:keymaster: MBM-3.0-hanoip_retail-bf902af-210611
(bootloader) git:storsec: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) gitrov: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:abl: MBM-3.0-hanoip_retail-aea4f158e7-210611
(bootloader) git:qupfw: MBM-3.0-hanoip_retail-6ac31cc-210611
(bootloader) git:uefisecapp: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D03162
(bootloader) primary-display: tm_ili7807s_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.269s

Hmm...according to this, you should be able to boot. Do you still see the same error? Can you boot into recovery and do a factory reset?

arsradu said:
Hmm...according to this, you should be able to boot. Do you still see the same error? Can you boot into recovery and do a factory reset?
Click to expand...
Click to collapse
When I boot into recovery mode, I got same error "No valid OS found. The device will not boot."

milan.vyas7 said:
When I boot into recovery mode, I got same error "No valid OS found. The device will not boot."
Click to expand...
Click to collapse
Hmmm that's interesting... You should have been able to boot into recovery from bootloader... Just use the arrow keys until you see recovery mode, then Power key to select. But if that doesn't work...then I don't know.
Can you boot a custom recovery and try the same thing?
To boot into twrp (without flashing it), you can do the following command:
fastboot boot /path-to-your-twrp.img
You can download it from here.

arsradu said:
Hmmm that's interesting... You should have been able to boot into recovery from bootloader... Just use the arrow keys until you see recovery mode, then Power key to select. But if that doesn't work...then I don't know.
Can you boot a custom recovery and try the same thing?
To boot into twrp (without flashing it), you can do the following command:
fastboot boot /path-to-your-twrp.img
You can download it from here.
Click to expand...
Click to collapse
Here is the output.
C:\platform-tools_r33.0.3-windows\platform-tools>fastboot boot twrp-3.6.2_12.1-0-hanoip-20220808-0701.img
Sending 'boot.img' (36600 KB) OKAY [ 0.792s]
Booting (bootloader) Fastboot boot command is not available in locked device
FAILED (remote: '')
fastboot: error: Command failed

Oh maaan... This sucks. Then I don't know...

arsradu said:
Oh maaan... Isso é uma merda. Então não sei...
Click to expand...
Click to collapse
Até agora não há como resolver esse problema sem usar jtag

Yeah, I'm not sure you can fix it without using the JTAG...
By the way, which Android version did you install before reaching this state?

arsradu said:
Yeah, I'm not sure you can fix it without using the JTAG...
By the way, which Android version did you install before reaching this state?
Click to expand...
Click to collapse
In this case he was on android 12 and tried to downgrade to 11, but in doing so he also blocked the bootloader and in that the system no longer allows to rewrite the rom