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.

I can't unlock bootloader

Hi*guys*I*tried*to*unlock*the*bootloader*of*my*cell*phonebut*when*placing*the*bootloader*log*tells*me*that*it*doesnot*qualify*my*device
This*is*the*record*of*get-var*all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.12
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322FQBR2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x1e
(bootloader) uid: E390CDC400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 351864087651315
(bootloader) meid:
(bootloader) date: 03-06-2019
(bootloader) sku: XT1601
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0:51:34 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-16/0400:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.41.15.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_22.29.02.70R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g2148ea10 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Wed Sep 5 10:00:37 CDT
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.12-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VB8.12-0-gc6ac81e
(bootloader) tz.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) devcfg.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) keymaster.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) cmnlib.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) cmnlib64.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) prov.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) aboot.git: git=MBM-NG-VB8.12-0-gf2e5426
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: retla1st
all: listed above

Gaxo said:
Hi*guys*I*tried*to*unlock*the*bootloader*of*my*cell*phonebut*when*placing*the*bootloader*log*tells*me*that*it*doesnot*qualify*my*device
This*is*the*record*of*get-var*all
Click to expand...
Click to collapse
What did you tried to unlock the bootloader?

lucki1000 said:
What did you tried to unlock the bootloader?
Click to expand...
Click to collapse
I tried from the Motorola page but it gives an error that the device does not qualify to unlock the bootloader

Gaxo said:
Hi*guys*I*tried*to*unlock*the*bootloader*of*my*cell*phonebut*when*placing*the*bootloader*log*tells*me*that*it*doesnot*qualify*my*device
This*is*the*record*of*get-var*all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.12
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322FQBR2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x1e
(bootloader) uid: E390CDC400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 351864087651315
(bootloader) meid:
(bootloader) date: 03-06-2019
(bootloader) sku: XT1601
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0:51:34 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-16/0400:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.41.15.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_22.29.02.70R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g2148ea10 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Wed Sep 5 10:00:37 CDT
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.12-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VB8.12-0-gc6ac81e
(bootloader) tz.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) devcfg.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) keymaster.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) cmnlib.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) cmnlib64.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) prov.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) aboot.git: git=MBM-NG-VB8.12-0-gf2e5426
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: retla1st
all: listed above
Click to expand...
Click to collapse
I'm confused
Your product device is listed as cedric (moto g5) but your sku is listed as XT1601 (moto g4 play)
Play device or amazon prime devices may not always be eligible for bootloader unlock

Gaxo said:
I tried from the Motorola page but it gives an error that the device does not qualify to unlock the bootloader
Click to expand...
Click to collapse
Did you allowed unlock bootloader in developer options?

Gaxo said:
I tried from the Motorola page but it gives an error that the device does not qualify to unlock the bootloader
Click to expand...
Click to collapse
TheFixItMan said:
I'm confused
Your product device is listed as cedric (moto g5) but your sku is listed as XT1601 (moto g4 play)
Play device or amazon prime devices may not always be eligible for bootloader unlock
Click to expand...
Click to collapse
here you have the solution :victory:

TheFixItMan said:
Hi*guys*I*tried*to*unlock*the*bootloader*of*my*cell*phonebut*when*placing*the*bootloader*log*tells*me*that*it*doesnot*qualify*my*device
This*is*the*record*of*get-var*all
I'm confused
Your product device is listed as cedric (moto g5) but your sku is listed as XT1601 (moto g4 play)
Play device or amazon prime devices may not always be eligible for bootloader unlock
Click to expand...
Click to collapse
Ok, this is weird. When I bought the second-hand device, the cell phone came with the bootloader unlocked. I had a report when I bought it, so I ordered it removed. I guess they changed the sku to unlock it. Is there a solution to change sku? As for example installing the original firmware by fastboot

Gaxo said:
Ok, this is weird. When I bought the second-hand device, the cell phone came with the bootloader unlocked. I had a report when I bought it, so I ordered it removed. I guess they changed the sku to unlock it. Is there a solution to change sku? As for example installing the original firmware by fastboot
Click to expand...
Click to collapse
You could try flashing stock firmware as long as it is actually a moto g5 (check the label under the battery)
You would need to flash gpt & bootloader to repartition
Firmware can be found
https://mirrors.lolinet.com/firmware/moto/cedric/official/
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
If you get security downgrade error when trying to flash gpt/bootloader the firmware you are trying to flash is too old

TheFixItMan said:
You could try flashing stock firmware as long as it is actually a moto g5 (check the label under the battery)
You would need to flash gpt & bootloader to repartition
Firmware can be found
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you get security downgrade error when trying to flash gpt/bootloader the firmware you are trying to flash is too old
Click to expand...
Click to collapse
I will try to flash the stock rom that is here, Since I was in Nougat and update to Oreo with the last published revision Give more details when you unlock it

It did not work, I have tried with the rom that you have given me and with all the stocks in this forum it still does not change the SKU

Gaxo said:
It did not work, I have tried with the rom that you have given me and with all the stocks in this forum it still does not change the SKU
Click to expand...
Click to collapse
Sounds to me like it could have possibly been a bricked phone and they have used some software/hardware to flash an image back onto it giving it that sku (which is odd as I worked with others to make a totally safe way to unbrick this device)
If after enabling adb debugging and enabling oem unlock if available if its saying your device is not eligible for unlock (assuming all codes have been entered correctly on the Motorola website) then there's not anything you can do
If I were you I'd contact the seller and question why your device displays the sku of a moto g4 play & obtain a refund for dodgy practices

I have a small idea, If I try to use the SD method with the Firmware that you have put in another thread and try to fully flash the cell phone including Bootllader (Since this cell phone is updated to 8.1 and I have flashed the bootloader of the rom) I may recover your Original Sku, right?

Gaxo said:
I have a small idea, If I try to use the SD method with the Firmware that you have put in another thread and try to fully flash the cell phone including Bootllader (Since this cell phone is updated to 8.1 and I have flashed the bootloader of the rom) I may recover your Original Sku, right?
Click to expand...
Click to collapse
The image tricks the phone into booting the bootloader from the sd card so a user without an accessable bootloader can then flash gpt which repartitions the device and then flash the bootloader back
I don't know how they changed the sku (probably by JTAG)
So the sd card probably wouldn't help if you have flashed gpt and bootloader from the latest firmware
You could always create the sd card and see if it gives you a different sku when it's inserted

TheFixItMan said:
Sounds to me like it could have possibly been a bricked phone and they have used some software/hardware to flash an image back onto it giving it that sku (which is odd as I worked with others to make a totally safe way to unbrick this device)
If after enabling adb debugging and enabling oem unlock if available if its saying your device is not eligible for unlock (assuming all codes have been entered correctly on the Motorola website) then there's not anything you can do
If I were you I'd contact the seller and question why your device displays the sku of a moto g4 play & obtain a refund for dodgy practices
Click to expand...
Click to collapse
Man, I'm already busting my head to unlock the boorloader of this thing, I'll leave it so I really don't have another G5 to test, It's intregant somehow how the hell they changed the sku to the cell phone Anyway, even so thanks for the help friend

Gaxo said:
Man, I'm already busting my head to unlock the boorloader of this thing, I'll leave it so I really don't have another G5 to test, It's intregant somehow how the hell they changed the sku to the cell phone Anyway, even so thanks for the help friend
Click to expand...
Click to collapse
My best guess is they used a JTAG and modified moto g4 play unbrick files to be able to flash the bootloader back to the G5 but who knows
I take it when you have typed
oem get_unlock_data
It gives you a key and you have copied this key into a text document and then removed all the spaces
The key is normally on about 4 lines so you need to remove all the spaces so it's just on one whole line then copy that very long string into the Motorola website

Help me flash this phone

Help me find compatible firmware to flash on fastboot my Moto G5 EU version 2/16GB
I try flash random clean stock 8.1 fw. But i have errorcant start system or enter recovery.
I cant start phone
Info from my phone is
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: XXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 625716AC00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: XXXXXX
(bootloader) meid:
(bootloader) date: 06-13-2017
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:40 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8937_22.29.02.69.01R CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.702s
C:\Program Files\Minimal ADB and Fastboot>
Any help will be apperciate. I really need this phone back to work. I want only flash clean stock 8.1.0 rom.
When i buyed this phone. But now i have semi brick.
Anyone here can help me?

Problem solved. I found newest 8.1.0 stock rom. I flashed and phone back to life.
Last problem what i have is i cant unlock bootloader.

Morricorne said:
Problem solved. I found newest 8.1.0 stock rom. I flashed and phone back to life.
Last problem what i have is i cant unlock bootloader.
Click to expand...
Click to collapse
Follow the process for unlocking on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Make sure usb debugging and oem unlock (if available) is enabled
Make sure the unlock string is correct and you have removed all spaces so its on one long single line as per instructions

TheFixItMan said:
Follow the process for unlocking on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Make sure usb debugging and oem unlock (if available) is enabled
Make sure the unlock string is correct and you have removed all spaces so its on one long single line as per instructions
Click to expand...
Click to collapse
This device is supported. But i have message This device isnt allowed to unlock bootloader. On Motorola site.
I follow every step on This guide
Still the same.
XT1676 EU 2/16 GB version here.
Stock Android 8.1.0 OPP28.85-19-4-2
This suck, cause i want try 64 os but os on This device. But cant

Morricorne said:
This device is supported. But i have message This device isnt allowed to unlock bootloader. On Motorola site.
I follow every step on This guide
Still the same.
XT1676 EU 2/16 GB version here.
Stock Android 8.1.0 OPP28.85-19-4-2
This suck, cause i want try 64 os but os on This device. But cant
Click to expand...
Click to collapse
Either the device is an amazon device or locked to a carrier which doesn't allow bootloader unlocking until the device is carrier unlocked (officially) or it has been previously unlocked in which case you would need to know the unlock code to unlock it again
If it has been registered before with Motorola you need to sign in using that email or try and unlink that address from the device (motorola device id option under settings)

https://imgur.com/cDPKjin
https://imgur.com/hblRtIU
Still no luck

TheFixItMan said:
Either the device is an amazon device or locked to a carrier which doesn't allow bootloader unlocking until the device is carrier unlocked (officially) or it has been previously unlocked in which case you would need to know the unlock code to unlock it again
If it has been registered before with Motorola you need to sign in using that email or try and unlink that address from the device (motorola device id option under settings)
Click to expand...
Click to collapse
I Just give up for good. I try many times, and cant unlock bootloader. I spend almost 5 hour today to figure out how ressurect this phone from dead. Its working and Its enough. Adreno 505/506 is to weak to emulate Dolphin And Citra emulator.
Time to buy something with new snapdragon cpu.
I buyed this moto from second hand for 10 euro today. Little cracked screen. But works. Its enough for me. Anyway thanks for all help i really apperciate it.

Morricorne said:
I Just give up for good. I try many times, and cant unlock bootloader. I spend almost 5 hour today to figure out how ressurect this phone from dead. Its working and Its enough. Adreno 505/506 is to weak to emulate Dolphin And Citra emulator.
Time to buy something with new snapdragon cpu.
I buyed this moto from second hand for 10 euro today. Little cracked screen. But works. Its enough for me. Anyway thanks for all help i really apperciate it.
Click to expand...
Click to collapse
Can you copy and paste the bootloader output of fastboot oem get_unlock_data (unedited) and I'll try and unlock it - I can't be bothered to manually type it in
If it gives the same for me then it can't be unlocked

Last question about bootloader and this device.
Root is needed to unlock bootloader on moto G5?
Maybe this is a problem. I dont have root access.

Morricorne said:
Last question about bootloader and this device.
Root is needed to unlock bootloader on moto G5?
Maybe this is a problem. I dont have root access.
Click to expand...
Click to collapse
You need to have an unlocked bootloader
Flash twrp
Flash magisk in twrp

I unlocked bootloader, flash twrp 64 bit. I now check lineageos 17 64 bit.
But battery life suck.
Time to find Best 64 bit rom.
Anyway thanks for help

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

Moto z2 wont make it past bootlogo, even with flashall XT1789-04 Please help

So, I have tried various flashalls to try and bring my device back to stock. It seems that no matter what I do, I am always stuck at the bootlogo which then will either hang or force restart (depends on the firmware). I have even tried to flash the hybrid android 9 firmware that is available hoping that the newer firmware would solve the issue but it always seems that no matter what I do I am stuck with the same problem. I have tried about 3 different tools for generating flashalls, and am watching each file write with success.
Each time I flash I do indeed see the changes, obviously I can see the new version info in fastboot, also the bootlogo changes depending on the firmware, I can also flash twrp with ease. Ive tried to install lineage with hopes that it would fix the issue but no.
Now I also have tried to boot to recovery post flash then back to system, also yields no boot for me.
I did notice, that if I try to go into EDL mode that I am thrown back into a bootloop. In fastboot RSD-lite can see the device but I am greeted with a message of cannot boot into fastboot if I try to use it. (Perhaps I am using RSD wrong and the first command is an adb command?)
I also noticed that while my bootloader background image on Partition A changes with each flash, My bootloader Background image on partition B is the same Black and white Motorola background. Lastly I am making sure I am using an old windows 7 computer for this process and my newer computer will recognize the device, but cannot write to it.
Ill be honest, I put this phone in a drawer after being stumped with it about a year ago, trying to bring it back to life now. Any help would be appreciated. Thank you all for the wonderful work you do here on this forum. <33

H411UCIN093NIC said:
So, I have tried various flashalls to try and bring my device back to stock. It seems that no matter what I do, I am always stuck at the bootlogo which then will either hang or force restart (depends on the firmware). I have even tried to flash the hybrid android 9 firmware that is available hoping that the newer firmware would solve the issue but it always seems that no matter what I do I am stuck with the same problem. I have tried about 3 different tools for generating flashalls, and am watching each file write with success.
Each time I flash I do indeed see the changes, obviously I can see the new version info in fastboot, also the bootlogo changes depending on the firmware, I can also flash twrp with ease. Ive tried to install lineage with hopes that it would fix the issue but no.
Now I also have tried to boot to recovery post flash then back to system, also yields no boot for me.
I did notice, that if I try to go into EDL mode that I am thrown back into a bootloop. In fastboot RSD-lite can see the device but I am greeted with a message of cannot boot into fastboot if I try to use it. (Perhaps I am using RSD wrong and the first command is an adb command?)
I also noticed that while my bootloader background image on Partition A changes with each flash, My bootloader Background image on partition B is the same Black and white Motorola background. Lastly I am making sure I am using an old windows 7 computer for this process and my newer computer will recognize the device, but cannot write to it.
Ill be honest, I put this phone in a drawer after being stumped with it about a year ago, trying to bring it back to life now. Any help would be appreciated. Thank you all for the wonderful work you do here on this forum. <33
Click to expand...
Click to collapse
RSD lite doesn't work with windows 10
What does getvar all say?
Code:
fastboot getvar all
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
RSD lite doesn't work with windows 10
What does getvar all say?
Code:
fastboot getvar all
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
No commands that have to do with writing work from my windows 10 PC. Its the reason I am using the windows 7 one for driver comparability.
From Windows 10 it say
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190608
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224C3BV6
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 8561DC86
(bootloader) verity-state: disabled (0)
And from Windows 7 it says:
C:\Users\Administrator\Desktop\final try>fastboot getvar all
< waiting for any device >
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190608
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224C3BV6
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 8561DC86
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356503080588174
(bootloader) meid:
(bootloader) date: 07-28-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3728
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1f14820 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Fri Sep 20 09:23:35 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190608
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190608
(bootloader) gitmic: MBM-3.0-nash_retail-4fc2afc-190608
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190608
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190608
(bootloader) gitrov: MBM-3.0-nash_retail-3537781-190608
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(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: no
(bootloader) slot-retry-count:_a: 2
(bootloader) slot-retry-count:_b: 5
all: listed above
finished. total time: 0.284s
Nice Guide BTW, I can tell you work very hard for this community

sd_shadow said:
RSD lite doesn't work with windows 10
What does getvar all say?
Code:
fastboot getvar all
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
When using LMSA it does not detect my phone properly. It says that my device info is: []
This is the result on both windows 10 and windows 7

H411UCIN093NIC said:
When using LMSA it does not detect my phone properly. It says that my device info is: []
This is the result on both windows 10 and windows 7
Click to expand...
Click to collapse
It appears you lost the baseband, so the LMSA cannot read IMEI and cannot flash....
Windows 7 or 10 does not matter....
Sent from my LG-LS997 using Tapatalk

cgigate said:
It appears you lost the baseband, so the LMSA cannot read IMEI and cannot flash....
Windows 7 or 10 does not matter....
lk
Click to expand...
Click to collapse
I have tried both of these Flashalls with no luck https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070 along with 8.0 oreo no luck then even tried the hybrid 9.0 version with no luck either. I saw a specific post where someone created a flashable with the ability to bring back baseband however, the file no longer exists on googledrive. You wouldnt happen to have it, would you?

H411UCIN093NIC said:
I have tried both of these Flashalls with no luck along with 8.0 oreo no luck then even tried the hybrid 9.0 version with no luck either. I saw a specific post where someone created a flashable with the ability to bring back baseband however, the file no longer exists on googledrive. You wouldnt happen to have it, would you?
Sent from my LG-LS997 using Tapata
Click to expand...
Click to collapse
You need build a new blankflash by yourself to save your device....(search the blankflash build guide in xda).
If you still don't know how, then trash it to go forward...
Sent from my LG-LS997 using Tapatalk

cgigate said:
You need build a new blankflash by yourself to save your device....(search the blankflash build guide in xda).
If you still don't know how, then trash it to go forward...
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
I forgot, this is where I was at a year ago xD. Ill look into it right now. Thank you very much for your help

cgigate said:
You need build a new blankflash by yourself to save your device....(search the blankflash build guide in xda).
If you still don't know how, then trash it to go forward...
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Found it, was actually linked to an old post I made a year ago (facepalm)
If anyone one else needs it its here
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5

cgigate said:
You need build a new blankflash by yourself to save your device....(search the blankflash build guide in xda).
If you still don't know how, then trash it to go forward...
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Using fastboot oem blankflash returns
(bootloader) Command Restricted

sd_shadow said:
RSD lite doesn't work with windows 10
What does getvar all say?
Code:
fastboot getvar all
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Happen to know an option for me if baseband is gone and fastboot oem blankflash returns that the bootloader is command restricted? Of course my device is indeed unlocked. I do not need cellular service for this phone, honestly don't even care if the phone turns into a brick, its this learning trial and error that excites me personally. If you know any methods that are even more so risky please let me know lol. I did have a question however, since I cannot get my phone to go into 9008 mode through fastboot oem blankflash will I be able to use an EDL shorting cable to push the device into QCM? I am only asking you, because you seem to be highly knowledgeable. Again, I don't care if the device turns into a paper weight or bursts into flames, so if there is anything more risky that you normally wouldn't suggest I am game. I am not shy to linux if there is a better way.

H411UCIN093NIC said:
Using fastboot oem blankflash returns
(bootloader) Command Restricted
Click to expand...
Click to collapse
Try to boot TWRP then Use
Code:
adb reboot edl
Sent from my ocean using XDA Labs

sd_shadow said:
Try to boot TWRP then Use
Code:
adb reboot edl
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply, but that has the same outcome. It just bootloops with the moto screen. I also tried a modded fastboot for the <fastboot reboot-edl command> with no luck either.