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.

Moto G5 stuck in bootloop

hi friends my moto g5 xt1677 is stuck in bootloop,able to access fastboot and recovery mode.I don't want to lose my data so is there any way I can get back my data.I have heard that if i update it to the latest security patch or current security patch i may be able to start my phone. I had december security patch installed.If anyone is having december ota file or february ota file please send the link.I am able to boot in recovery mode
recovery mode version below
motorola/cerdric_retail/cedric 8.1.0/OPPS28.85-19-2/73f5
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=07 FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3222CC4J
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc4
(bootloader) uid: 2A7E7F7700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358222070469919
(bootloader) meid:
(bootloader) date: 03-08-2017
(bootloader) sku: XT1677
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Dec 20 6:49:17 UTC 2018"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-ga87df5f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Dec 20 00:55:53 CST
(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=3213759-dirty
(bootloader) devcfg.git: git=3213759-dirty
(bootloader) keymaster.git: git=3213759-dirty
(bootloader) cmnlib.git: git=3213759-dirty
(bootloader) cmnlib64.git: git=3213759-dirty
(bootloader) prov.git: git=3213759-dirty
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: amzin
(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.247s
C:\adb>

Flash stock firmware via fastboot without erasing user data
If it doesn't boot or bootloops you will have to erase userdata
https://mirrors.lolinet.com/firmware/moto/cedric/official/

G5
TheFixItMan said:
Flash stock firmware via fastboot without erasing user data
If it doesn't boot or bootloops you will have to erase userdata
can you guide me how to do this
Click to expand...
Click to collapse

G5
TheFixItMan said:
Flash stock firmware via fastboot without erasing user data
If it doesn't boot or bootloops you will have to erase userdata
can you guide me how to do this i dont want to lose my data
Click to expand...
Click to collapse

You could Google flash stock firmware moto g5
I've already provided link to firmware
If your phone bootloops etc you may have no choice but to erase data
Put phone in fastboot mode
Connect phone to PC via USB
Open a terminal/cmd window where you have fastboot files (Google is your friend) and firmware
Type the following in terminal window/cmd
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 (only if you want to erase data or phone bootloops etc)
fastboot oem fb_mode_clear
fastboot reboot

I have problems to find a suitable firmware for my cedric 1676 (EU/Germany). The fastboot-Commands did not work with the rom-Versions out of the "RETAIL"-Folder.
--> Finally I had siccess with a version from the "RetEU"-Folder (perhaps "EU" means European Union?)...
some aditional informations about suitable versions.
https://www.hardreset.info/devices/motorola/motorola-moto-g5/faq/firmware-flash/
Now I want to return to Nougat (downgrade from Oreo to Nougat). I have a few questions:
- Can I use TWRP for downgrade to a Nougat Rom (Carbon Rom)?
- Which TWRP should I use (normal or 64bit)?
- Is there anything else to note?

Mobilettchen said:
I have problems to find a suitable firmware for my cedric 1676 (EU/Germany). The fastboot-Commands did not work with the rom-Versions out of the "RETAIL"-Folder.
--> Finally I had siccess with a version from the "RetEU"-Folder (perhaps "EU" means European Union?)...
some aditional informations about suitable versions.
https://www.hardreset.info/devices/motorola/motorola-moto-g5/faq/firmware-flash/
Now I want to return to Nougat (downgrade from Oreo to Nougat). I have a few questions:
- Can I use TWRP for downgrade to a Nougat Rom (Carbon Rom)?
- Which TWRP should I use (normal or 64bit)?
- Is there anything else to note?
Click to expand...
Click to collapse
Here is the firmware for your device
https://mirrors.lolinet.com/firmware/moto/cedric/official/TEFES/
If you still want to downgrade from oreo to nougat then just don't flash the gpt and bootloader, if you flash the device will hard bricked.
For custom roms you can use carbon ROM.
You need 64 bit twrp to flash.

@riyan65 - many thx for tips & support, and greetings to india
Why do you think that the "TEFES"-Version instead of "RetEU" (or even "RETAIL") ist suitable for European-specific radio bands?

Mobilettchen said:
@riyan65 - many thx for tips & support, and greetings to india
Why do you think that the "TEFES"-Version instead of "RetEU" (or even "RETAIL") ist suitable for European-specific radio bands?
Click to expand...
Click to collapse
For xt1676 the device firmware is TEFES, so I recommend you that firmware, if you want other firmware like retail or reteu you can flash it that also.

riyan65 said:
For xt1676 the device firmware is TEFES, so I recommend you that firmware, if you want other firmware like retail or reteu you can flash it that also.
Click to expand...
Click to collapse
OK - But TEFES is just *one* Software Channel, supporting the Cedric, in a specific Country. (NOT EU). I try it out. After Flashing the "Lenovo Moto Smart Assistent" did not recocnize my Cedric (no entry on "Software Chanel"). Retail is working on my phone

Mobilettchen said:
OK - But TEFES is just *one* Software Channel, supporting the Cedric, in a specific Country. (NOT EU). I try it out. After Flashing the "Lenovo Moto Smart Assistent" did not recocnize my Cedric (no entry on "Software Chanel"). Retail is working on my phone
Click to expand...
Click to collapse
Oh sorry I forgot to tell that, which ever software channel you flash nothing will happen as the device is not going to receive any more software updates so it does not affect any thing, as for cellular every firmware will work for every country.

[Help Thread][Moto G5S](2017) Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Moto G5S
2017
XT1793, XT1794 (Europe, India)
XT1795 (India)
XT1792 (Brazil)
​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button, in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
[Index]Motorola Flashing Utilities, Firmware, and more
Index for Device Thread Link
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
​

I'm not planning on adding every Rom or Mod,
but if you have a suggestion for other links
Please post them here.
FAQs
UnLocking the Bootloader
ReLocking the Bootloader
[Fixing] Baseband <not found> / IMEI=0 / No Network After Flash / Issues
Fixing your Moto stuck in Qualcomm QHSUSB_Bulk or qloader mode
Using Lenovo's MOTO Smart Assistant to Update/Repair/Backup
Custom Roms/Recovery/Root/
Firmware
https://mirrors.lolinet.com/firmware/moto
Specs

Hey! I recently got this specific device with 32 GB of internal storage (non plus model) I have about 3 devices of Android modding experience. Is it recommended to unlock it and put a custom ROM on it? Or should I stay stock???

Some random said:
Hey! I recently got this specific device with 32 GB of internal storage (non plus model) I have about 3 devices of Android modding experience. Is it recommended to unlock it and put a custom ROM on it? Or should I stay stock???
Click to expand...
Click to collapse
Whether a custom rom is a good option is really your decision.
In general moto stock rom is more stable and battery efficient,
but Moto often is slow with security patches and new Android versions.
Custom roms offer newer Android versions customizations and features.
If you unlock the bootloader, it may not be easy to relock.
Sent from my mata using XDA Labs

Thank you for the feedback! Guess I will unlock as soon as the first Android 10 ROM is out (or smthn else big)

Hi, I need help. My Moto G5S (XT1794) was on stock ROM but beginning to have issues with apps crashing and even occasionally rebooting randomly. I decided to see if a change of OS would do it some good. I've flashed plenty of phones previously with Cyanogenmod and LineageOS so I'm not exactly a noob but I'm just following the simple steps.
I used this thread to find links to the builds, TWRP and GApps:
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-16-0-t3911496
I unlocked the bootloader, loaded twrp-3.3.1-1-montana.img and then flashed LineageOS 16.0 v0.15. Every time I reboot I get the 'can't be trusted' warning message (which I understand is normal), then the LineageOS boot screen appears for quite a long time cycling, then the phone simply reboots back into TWRP. I've tried using LineageOS 16.0 v0.14 and either flashing GApps or not with the same results. I've even tried twrp-3.3.1-0-montana.img and wiping the caches after each install.
In desperation I tried to flash back to stock ROM from here but the flash fails:
https://mirrors.lolinet.com/firmware/moto/montana/official/RETGB/
I'm out of ideas! Can anyone help?

bifter said:
Hi, I need help. My Moto G5S (XT1794) was on stock ROM but beginning to have issues with apps crashing and even occasionally rebooting randomly. I decided to see if a change of OS would do it some good. I've flashed plenty of phones previously with Cyanogenmod and LineageOS so I'm not exactly a noob but I'm just following the simple steps.
I used this thread to find links to the builds, TWRP and GApps:
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-16-0-t3911496
I unlocked the bootloader, loaded twrp-3.3.1-1-montana.img and then flashed LineageOS 16.0 v0.15. Every time I reboot I get the 'can't be trusted' warning message (which I understand is normal), then the LineageOS boot screen appears for quite a long time cycling, then the phone simply reboots back into TWRP. I've tried using LineageOS 16.0 v0.14 and either flashing GApps or not with the same results. I've even tried twrp-3.3.1-0-montana.img and wiping the caches after each install.
In desperation I tried to flash back to stock ROM from here but the flash fails:
https://mirrors.lolinet.com/firmware/moto/montana/official/RETGB/
I'm out of ideas! Can anyone help?
Click to expand...
Click to collapse
Are you doing the fastboot -w
Before flashing lineage OS!
Sent from my mata using XDA Labs

sd_shadow said:
Are you doing the fastboot -w
Before flashing lineage OS!
Click to expand...
Click to collapse
Tried again, like this?
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 535822336 bytes
sending 'recovery' (15850 KB)...
OKAY [ 0.517s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.250s]
finished. total time: 0.797s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
wiping cache...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.110s]
erasing 'cache'...
OKAY [ 0.000s]
finished. total time: 0.125s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
No joy! I proceeded to flash the latest LineageOS and GApps images (with some errors about not being able to mount cache partition, etc) but now the phone is simply rebooting to the bootloader (after 10 minutes on the OS bootscreen). From there I can boot into recovery again.

bifter said:
Tried again, like this?
No joy! I proceeded to flash the latest LineageOS and GApps images (with some errors about not being able to mount cache partition, etc) but now the phone is simply rebooting to the bootloader (after 10 minutes on the OS bootscreen). From there I can boot into recovery again.
Click to expand...
Click to collapse
Don't know
When you flashed stock did you use
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 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
Or something else.
Sent from my mata using XDA Labs

sd_shadow said:
Don't know
When you flashed stock did you use
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 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
Or something else.
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Sorry, had to go to bed as I had an early start. I followed a similar procedure but not from an XDA forum and I guess someone got the steps wrong! I found an alternative post on XDA which eventually worked for me. (Flashing the gpt.bin failed the first time round so I left that out and there were 9 sparsechunk files.) I'm now back at stock ROM and it immediately received an OTA security update, now shows:
Android version: 8.1.0
Current version: OPPS28.65-37-7-11
Security patch level: August 1, 2019
It's not clear to me if this is up to date, the Motorola Web site is full of broken links.
The original reason for installing a custom ROM was because the phone was becoming laggy, some apps were crashing and occasionally the phone was rebooting randomly. I think I'll wait and see if this is resolved as I don't fancy going back through that Faustian loop again. Thanks for taking the time to help.

I have the xt1799-2, can i flash the firmware of any of these versions on that phone?
if yes, do i need to flash a rom if i just want to use stock oreo?
Can I just flash the update directly, or do I need to flash to 7.1.1 and then update?
Source Files:
https://mirrors.lolinet .com/firmware/moto/montana/
Thanks so much, I've been trying to figure this out for over 10 hours.
sd_shadow said:
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Moto G5S
2017
XT1793, XT1794 (Europe, India)
XT1795 (India)
XT1792 (Brazil)
​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button, in lieu of simply posting "Thank you".
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
[Index]Motorola Flashing Utilities, Firmware, and more
Index for Device Thread Link
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
​
Click to expand...
Click to collapse

Moto G5s xt1792 HARDEST brick
Hello,
I'd like to know if it's worth getting a micro SD for trying the mmcblk0.img flashing, because for what it sounds, I don't see a way it would work.
Considerations:
Rescue and Smart Assistant (LMSA) tried. First times, it did recognized the device but failed on 80%; after about two tries, it stopped recognizing the device;
All drivers for usb installed;
I can only get commands working through fastboot;
Trying to flash a stock rom through fastboot returns bootloaders errors for every command;
No adb commands work;
Blank Flash doesn't recognized any connected devices.
This is what cmd returns me for "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 3
(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: 2e1801a1
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: E37B906C00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from normal boot mode
(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-VBC.12-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.065s
If the info above isn't enough, please, guide me into getting the info you need to help solving this issue, or — at least — giving me the relief of knowing I'm not throwing my money away for buying another phone.
Thank you very much in advance!

phkoon said:
Hello,
I'd like to know if it's worth getting a micro SD for trying the mmcblk0.img flashing, because for what it sounds, I don't see a way it would work.
Considerations:
Rescue and Smart Assistant (LMSA) tried. First times, it did recognized the device but failed on 80%; after about two tries, it stopped recognizing the device;
All drivers for usb installed;
I can only get commands working through fastboot;
Trying to flash a stock rom through fastboot returns bootloaders errors for every command;
No adb commands work;
Blank Flash doesn't recognized any connected devices.
This is what cmd returns me for "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 3
(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: 2e1801a1
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: E37B906C00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from normal boot mode
(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-VBC.12-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.065s
If the info above isn't enough, please, guide me into getting the info you need to help solving this issue, or — at least — giving me the relief of knowing I'm not throwing my money away for buying another phone.
Thank you very much in advance!
Click to expand...
Click to collapse
The device must be in EDL mode to use a blankflash, mmcblk0 or loader.img
Looks like the bootloader is locked, so you cannot force it to EDL mode.
Only fastboot commands work in fastboot mode.
If you have a windows 7 PC try RSD Lite, it doesn't work well with most win 10 machines.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs

sd_shadow said:
The device must be in EDL mode to use a blankflash, mmcblk0 or loader.img
Looks like the bootloader is locked, so you cannot force it to EDL mode.
Only fastboot commands work in fastboot mode.
If you have a windows 7 PC try RSD Lite, it doesn't work well with most win 10 machines.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
I'll try it out and get back with the results, thanks for your reply.

What is the best ROM for gaming? I could only play on stock 8.1 arm32 and I noticed that the roms that are all arm64 have problems with games, for example crashes and heating above normal.

XT-1675 with locked bootloader [HELP]

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

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

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

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

This is because the boot.img you flashed is not signed by Motorola and its failing to pass verification
If you were trying to unlock the bootloader you should have followed the correct process and enabled adb and oem unlock from the dev options
Never flash firmware on a locked bootloader - if it goes wrong you have no chance of correcting it
You basically have two options now
Try and find firmware that will flash fully on your device
Firmware can be found here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Or take to a repair shop for either a motherboard replacement or if possible flashing with a jtag

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