Develop Bugs

Cannot lock my bootloader, progress is stopped by "still need signed oem/system.img"

Cannot lock my bootloader, progress is stopped by "still need signed oem/system.img"
I want to lock my bootloader, I don't want to lose my Software status: Official flag in fastboot mode
when I run fastboot getvar all this appears( IMEI and SN changed for privacy reasons)
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.23
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=07 FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: (changed for privacy)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 3415337500000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (changed for privacy)
(bootloader) meid:
(bootloader) date: 03-08-2017
(bootloader) sku: XT1676
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 3 3:14:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPPS25.
(bootloader) ro.build.fingerprint[1]: 137-72-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.246.4.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g517c70f-0010
(bootloader) kernel.version[1]: 6-g2ab6438 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Aug
(bootloader) kernel.version[3]: 4 04:33:06 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VB8.23-0-g2cafa24
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) devcfg.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) keymaster.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) cmnlib.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) prov.git: git=MBM-NG-VB8.09-0-g1a41aff
(bootloader) aboot.git: git=MBM-NG-VB8.23-0-g8fcce1f
(bootloader) qe: qe 0/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
all: listed above
and when I run
Code:
fastboot oem lock
I get
Code:
(bootloader) Still require signed system.img and/or oem.img
OKAY [ 0.014s]
finished. total time: 0.016s

Have you done
fastboot oem lock begin
flash stock firmware - all of it using fastboot commands
fastboot oem lock
You can't just do fastboot oem lock without doing the previous commands
Why do you want to lock the bootloader? There's no benefit unless you are selling the phone

Except that if I'm using stock with no root whatsoever, it's not worth having a message shaming you for unlocking your bootloader every time you boot or reboot
Also, I had issues beforehand doing the method you suggested, so that is why I'm not bothering with it

ap4ss3rby said:
Except that if I'm using stock with no root whatsoever, it's not worth having a message shaming you for unlocking your bootloader every time you boot or reboot
Also, I had issues beforehand doing the method you suggested, so that is why I'm not bothering with it
Click to expand...
Click to collapse
You can get rid of that message easily
Flash this in twrp recovery
https://drive.google.com/file/d/0B4BcNVrbrBOzZko3VjhmRWtrVms/view

TheFixItMan said:
You can get rid of that message easily
Flash this in twrp recovery
https://drive.google.com/file/d/0B4BcNVrbrBOzZko3VjhmRWtrVms/view
Click to expand...
Click to collapse
Not what I intend, also NO TWRP (Software Status: official in fastboot)

ap4ss3rby said:
Not what I intend, also NO TWRP (Software Status: official in fastboot)
Click to expand...
Click to collapse
My software status is official & I have twrp
Just flash twrp
Flash the zip file given to remove unlocked bootloader warning
Flash stock recovery if you don't want twrp

TheFixItMan said:
My software status is official & I have twrp
Just flash twrp
Flash the zip file given to remove unlocked bootloader warning
Flash stock recovery if you don't want twrp
Click to expand...
Click to collapse
Oh, will download, or just extract logo.bin from the zip, and flash it using fastboot commands

ap4ss3rby said:
Oh, will download, or just extract logo.bin from the zip, and flash it using fastboot commands
Click to expand...
Click to collapse
yes you can do that

TheFixItMan said:
yes you can do that
Click to expand...
Click to collapse
Thanks, flashed your logo.bin via fastboot and bootloader warning was gone. Though it reads "bad key" displayed on top of the stock Motorola logo.
A way to get rid of that too to have clean stock look?

No_Signal said:
Thanks, flashed your logo.bin via fastboot and bootloader warning was gone. Though it reads "bad key" displayed on top of the stock Motorola logo.
A way to get rid of that too to have clean stock look?
Click to expand...
Click to collapse
See
https://forum.xda-developers.com/g5/themes/motorola-boot-logo-n-removed-t3663735/post74065607
Please browse the Moto G5 threads - much quicker looking yourself & you can see what else is available

TheFixItMan said:
See
https://forum.xda-developers.com/g5/themes/motorola-boot-logo-n-removed-t3663735/post74065607
Please browse the Moto G5 threads - much quicker looking yourself & you can see what else is available
Click to expand...
Click to collapse
Those threads are known to me as those came up after after I did a look up myself.
No_Signal said:
A way to get rid of that too to have clean stock look?
Click to expand...
Click to collapse
That's why I explicit asked for "clean stock look", no fancy boot logo but original one without the "bad key" showing up.
"bad key" showing up ain't a problem of the boot graphics afaik. I didn't got it fixed myself though correct firmware/cedric image was flashed.

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.

Bought a bricked XT1789-06 for cheap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Start Up failed Motorola One Macro Worked

Start Up Failed Motorola One Macro and blank flash part 2 SUPPORT MODELS 2016-1 AND 2016-2
The model is showing in fastboot mode
1 FILES TO DOWNLOAD
Blank flash model 2016-1 https://mega.nz/file/WVdFiA5S#j07ZjTErq2WLxCMjCn1sNcX94_I9JoJMr4BKb0dwgYw
Blank flash model 2016-2
https://mega.nz/file/zF8xBbBR#ipUyowL4DNVCm_2hApjQ8qUQHdZHlRG0eY43PvQbVTA
Bat file
https://mega.nz/file/yJ1zDT5T#Ki2MSN_THjpX4e5Ec_skq5oY1dz0jBsS2iqdhJQusFM
USB drivers Motorola One Macro
https://mega.nz/file/bY0B3AjJ#mOs6TjEIbsuv1GgBwVXEcoBaq9hgBehe4_PSx529pPg
Mediatek Platform Tools*
https://mega.nz/file/CEFljaJK#4q2lFy8xAD_5tjyyxPh2B4RR3V6pF9BenzNmUSciXJI
FOLLOW STEPS HERE Thanks by
VD171
https://forum.xda-developers.com/mo...recover-how-unbrick-bricked-motorola-t4145191
For people speak spanish search Youtube channel Eufracio López and find the video with the same topic of name .
Any doubts don't forget to leave a comment below

post does not have bat file link

Ansaritech said:
post does not have bat file link
Click to expand...
Click to collapse
available new video
NOW SUPPORTING MODELS 2016-1 AND 2016-2
Mod edit: video has been removed

Successfully Worked
yehison said:
available new video
Thanks Bhai You saved my life my phone is now boot up and working perfectly!
Click to expand...
Click to collapse

This fix doesn`t work for me ,i am with unlocked bootloader ,and i was using android 10 GSI ,i have decided to switch back to stock, but neither blankflash helps ,neither flashing stock rom via fastboot, RSD Lite cannot read none of the .xml files in 5 different stock firmwares ,my bootloader is unlocked ,but when i type the command : fastboot flashing get_unlock_ability ,i get the result:
(bootloader) Flashing Android images permitted
OKAY [ 0.000s]
finished. total time: 0.000s
And when i try again with this command: fastboot flashing unlock , i get the result :
...
(bootloader) Already unlocked for flashing.
OKAY [ 0.000s]
finished. total time: 0.000s
What the heck is wrong? Please help ,i have tried everything that i can think of! My thoughts are that something is preventing reflashing partitions.I don`t have any errors during flash stock firmware process,but as far as i can see from the command: fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=00 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: MT6771V/WL
(bootloader) serialno:
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid:
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) imei: **********
(bootloader) imei2: *********
(bootloader) meid:
(bootloader) date: 09-28-2019
(bootloader) sku: XT2016-1
(bootloader) carrier_sku: XT2016-1
(bootloader) battid:********
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 5 22:28:20 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_retail/lima:10/QQ3A.
(bootloader) ro.build.fingerprint[1]: 200605.002.A1/200618:userdebug/tes
(bootloader) ro.build.fingerprint[2]: t-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V16.03.01.90R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 33) (Android (4691093 based on r316199)
(bootloader) kernel.version[2]: clang version 6.0.2 (https://android.goo
(bootloader) kernel.version[3]: glesource .com/toolchain/clang 183abd29fc
(bootloader) kernel.version[4]: 496f55536e7d904e0abae47888fc7f) (https:/
(bootloader) kernel.version[5]: /android.googlesource.com/toolchain/llvm
(bootloader) kernel.version[6]: 34361f192e41ed6e4e8f9aca80a4ea7e9856f32
(bootloader) kernel.version[7]: 7) (based on LLVM 6.0.2svn)) #1 SMP PREE
(bootloader) kernel.version[8]: MPT Thu Apr 30 10:59:26 CDT 2020
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.013s
Tried to unbrick the device with latest firmware version 81-5 and the version before the brick - 81-3 ,tested with several fastboot variants (minimal adb and fastboot, mfastboot and etc. ,latest versions) Even tried to unbrick the device on Windows 7 ,Windows 10 , Linux Mint 19.3 ,linux Mint 20 . When i try to unlock critical bootloader partitions ,fastboot says that i need an OEM signed bootloader, i have flashed the stock boot.img several times and i still get this message,is there any way to fully unlock the bootloader ? I am so upset that this device doesn`t have at least custom recovery.This was my last Moto/Lenovo device for sure! Just need to bring it back to life so i can get rid of it. MTK sucks!!!!

nikoman1987 said:
This fix doesn`t work for me ,i am with unlocked bootloader ,and i was using android 10 GSI ,i have decided to switch back to stock, but neither blankflash helps ,neither flashing stock rom via fastboot, RSD Lite cannot read none of the .xml files in 5 different stock firmwares ,my bootloader is unlocked ,but when i type the command : fastboot flashing get_unlock_ability ,i get the result:
(bootloader) Flashing Android images permitted
OKAY [ 0.000s]
finished. total time: 0.000s
And when i try again with this command: fastboot flashing unlock , i get the result :
...
(bootloader) Already unlocked for flashing.
OKAY [ 0.000s]
finished. total time: 0.000s
What the heck is wrong? Please help ,i have tried everything that i can think of! My thoughts are that something is preventing reflashing partitions.I don`t have any errors during flash stock firmware process,but as far as i can see from the command: fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_retail-210600d2e-200625
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=00 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZY326RQDMX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 21E0CC0B7AE344EA000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) imei: 3572301007*****
(bootloader) imei2: 3572301007*****
(bootloader) meid:
(bootloader) date: 09-28-2019
(bootloader) sku: XT2016-1
(bootloader) carrier_sku: XT2016-1
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 5 22:28:20 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_retail/lima:10/QQ3A. - this might be the issue too
(bootloader) ro.build.fingerprint[1]: 200605.002.A1/200618:userdebug/tes
(bootloader) ro.build.fingerprint[2]: t-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found> i think this is one of the issues
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V16.03.01.90R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 33) (Android (4691093 based on r316199)
(bootloader) kernel.version[2]: clang version 6.0.2 (https://android.goo
(bootloader) kernel.version[3]: glesource .com/toolchain/clang 183abd29fc
(bootloader) kernel.version[4]: 496f55536e7d904e0abae47888fc7f) (https:/
(bootloader) kernel.version[5]: /android.googlesource.com/toolchain/llvm
(bootloader) kernel.version[6]: 34361f192e41ed6e4e8f9aca80a4ea7e9856f32
(bootloader) kernel.version[7]: 7) (based on LLVM 6.0.2svn)) #1 SMP PREE
(bootloader) kernel.version[8]: MPT Thu Apr 30 10:59:26 CDT 2020
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: unknown - this prevents the device to be recovered with Moto Rescue and Smart assistant!!!
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C58429
all: listed above
finished. total time: 0.013s
Tried to unbrick the device with latest firmware version 81-5 and the version before the brick - 81-3 ,tested with several fastboot variants (minimal adb and fastboot, mfastboot and etc. ,latest versions) Even tried to unbrick the device on Windows 7 ,Windows 10 , Linux Mint 19.3 ,linux Mint 20 . When i try to unlock critical bootloader partitions ,fastboot says that i need an OEM signed bootloader, i have flashed the stock boot.img several times and i still get this message,is there any way to fully unlock the bootloader ? I am so upset that this device doesn`t have at least custom recovery.This was my last Moto/Lenovo device for sure! Just need to bring it back to life so i can get rid of it. MTK sucks!!!!
Click to expand...
Click to collapse
Please, give a try: MOD EDIT: Link Removed
It worked for my bricked one macro lima.

VD171 said:
Please, give a try: MOD EDIT: Link Removed
It worked for my bricked one macro lima.
Click to expand...
Click to collapse
The problem is that I don't speak Spanish , tried to follow only the video , and it didn't do the job , that was the first thing that I have tried...

nikoman1987 said:
The problem is that I don't speak Spanish , tried to follow only the video , and it didn't do the job , that was the first thing that I have tried...
Click to expand...
Click to collapse
I've translated the tutorial to english and to portuguese: https://forum.xda-developers.com/mo...recover-how-unbrick-bricked-motorola-t4145191
Please, try it and let me know if you can understand the steps.
Good luck

VD171 said:
I've translated the tutorial to english and to portuguese: https://forum.xda-developers.com/mo...recover-how-unbrick-bricked-motorola-t4145191
Please, try it and let me know if you can understand the steps.
Good luck
Click to expand...
Click to collapse
Ok ,Thanks in advance ,i will try it !
EDIT: This time it worked ,the problem was with platform tools or the blankflash file,because i have followed the the steps hundreds of times without luck... Many thanks!

yehison said:
Motorola One Macro with terrify problem.
You can try to get a solution with commands adb and scripts following this video.
Read description of video.
Steps by steps.
If you can't speak Spanish use Google translate.
The problem was solved successfully.
Mod edit: video has been removed
File Bat here https://mega.nz/file/bY0B3AjJ#mOs6TjEIbsuv1GgBwVXEcoBaq9hgBehe4_PSx529pPg
Any questions don't forget to leave below.
Solved !
Click to expand...
Click to collapse
Thank you for your great work! This tutorial totally helped me unbrick my Motorola one Macro .With a lot of help with correct translation ,everything worked perfect! After one month of hopelesness my device is like brand new!
And few things for the users with this issue: IT IS VERY IMPORTANT TO USE BLANKFLASH FOR YOUR EXACT DEVICE!!! (XT2016-1 or XT2016-2) AS WELL YOU WILL NEED THE CORRECT MTK PLATFORM-TOOLS ,OR FLASHING WON`T DO THE TRICK! AND ALWAYS USE THE LATEST STOCK FIRMWARE!

I understand perfectly all comments. I'll edit this post coming soon.

Something for motorola one (xt1941-3)?

J4m3sB4rn3s said:
Something for motorola one (xt1941-3)?
Click to expand...
Click to collapse
I'm working for this device visit my youtube channel .

mi motorola one macro estaba root y lo quise formatear de frabrica por fastboot y quedo en start up failded que hago

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?