Develop Bugs

Help for Motorola XT1672

Good evening,
first I apologize for my English, sometimes I write sometimes, for the technical terms I use the translator. I have a problem with my Motorola G5 and I try to explain it here trusting in a help
I found in my taxi a Motorola G5 XT1672, despite having brought it with me for several days in the taxi to make me contact, the owner (Brazilian) did not feel. After about a month I decided to keep it. It's a shame to throw it.
Not being very practical of phones I thought that with a reset I would put everything back instead I messed up everything since it has the protection of Google account. The USB debugging was not enabled, so any attempt to communicate with the device is not successful.
I thought then that by running a firmware flash I could restore it and finally use it but just do not know which way to start.
Thanks for the help
Kingfaber

Find the correct firmware for your device and then you use fastboot to flash it
Once you have fastboot installed & setup on. your pc & you have the correct firmware the commands are
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img (skip this one to avoid hard bricking)
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

Phone cannot use Wifi or Mobile Data

I flashed stock firmware onto my phone (the last file on https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/XT1789-04/) to unbrick my phone using this batch file:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.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 system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
I was able to successfully boot up the phone but the wifi and mobile data does not work. I cannot turn on the wifi and it does not give me the option to turn on mobile data even when my sim card is inserted. Any ideas on how to fix this would help.
Additional info: It was previously bricked because I deleted app_process32 from system/bin. It worked fine until I also uninstalled systemless xposed. I tried to flash Lineage OS but that just removed TWRP and still put me in a bootloop so then I did what I described above.

I remember the post where you said you had deleted that file, I believe you said you were on TMO. If so, flash this one, it newer than the oreo you flashed. Most likely the downgrade that is causing your problems.

Do a factory reset from stock recovery

I remember the post where you said you had deleted that file, I believe you said you were on TMO. If so, flash this one, it newer than the oreo you flashed. Most likely the downgrade that is causing your problems.
Click to expand...
Click to collapse
Thank you so much! You saved me $375 :')

OEM Unlocking Greyed out "flashing_unlocked" in fastboot?

I decided to go back to stock when I learned that the device is receiving Oreo (a bit far too late IMO), but for whatever reason, Android confirms that my bootloader is unlocked, but will not agree to allow me to run
fastboot oem lock to lock the bootloader. Any idea on how to fix this?

ap4ss3rby said:
I decided to go back to stock when I learned that the device is receiving Oreo (a bit far too late IMO), but for whatever reason, Android confirms that my bootloader is unlocked, but will not agree to allow me to run
fastboot oem lock to lock the bootloader. Any idea on how to fix this?
Click to expand...
Click to collapse
Once you have download stock firmware run these commands in fastboot
Note all data on the internal storage will be erased including pictures downloads etc
fastboot oem lock begin
fastboot oem fb_mode_set
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 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 oem lock

My Device doesn't turn on anymore

I was suppose to relock my bootloader, looked on YouTube and Google for answers. And tried this set of commands in the Cmd:
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
At the commands "flash oem oem.img" down to "fastboot flash system system.img_sparsechunk.4", it says that it failed at the end. I tried three times, still the same thing, so I got desperate to fix the issue and looked on google how to relock bootloader again.
And I just found another set of commands from a website to start off the process:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
At the end, my phone just ends up dead, I tried turning on back to fastboot mode, it didn't worked. i tried turing it on like how we usually turn it on, same results. I tried charging the phone, the same nothingness we see when our phones are off, and I know that I charged my phone before attempting to relock bootloader.
And I think I just bricked my phone.
Edit: I'm using a Moto G5 [cedric]

Never try and relock the bootloader once you have unlocked it - there is just no point as if you don't do it right you will destroy your device & if you do lock the bootloader without flashing the firmware correctly you may never be able to flash the correct firmware or do it properly again (without specialist equipment)
The first set of instructions you did would never work as for this device there are 9 sparsechunks 0-8
The second set of instructions would not have locked your bootloader but would have just re-flashed stock firmware
The chances are you either flashed the wrong firmware or you tried to flash old firmware and corrupted your gpt & bootloader
If you can't get into your bootloader then follow my guide below step by step exactly - however you may only be only to re-flash firmware if your device is bootloader unlocked as you may get validation errors when trying to reflash gpt & bootloader
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012

Help. The smartphone does not see the USB

Sorry for my english, translated by google
Hi. Can someone help or at least tell you in which direction to look. Moto (lenovo) G5 XT1675 cedric RETGB device. CEDRIC_OPP28.85_19_4_2_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml (the latest firm on Android 8.1.0) and over it via tvrp lightweight stock on 7.0 android was flashed. In search of a problem, I went through a lot: I replaced the board with yusb, flashed the Rescue and Smart Assistant program from Lenovo (with the firmware that the program told me), unlocked the bootloader + tvrp and root. I tried a lot of custom, but I didn’t solve the problem. The essence is the phone in the included state. does not see usb (in any way, neither charging nor connecting to a computer) but it is worth rebooting the device with the cable connected and everything works. But if you disconnect the phone cable. It no longer sees it until the next reboot. If the menu is loaded into Factory mode through the fastboot without connecting. cable, then when the bodies are connected, it sees it but only the first time. comp. the bodies are normally charged, stitched, etc., the TVRP also does not see the cable (also resolves with a reboot) I personally think about the bootloader, but having the latest version, there is nothing to update and it is risky to roll back to a version below (you can get a brick that cannot be cured with a simple firmware)

I say the same to most people with these types of issue
If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
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
Note backup any personal files from internal storage to your pc first

TheFixItMan said:
I say the same to most people with these types of issue
If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
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
Note backup any personal files from internal storage to your pc first
Click to expand...
Click to collapse
Thank you. I know about all this. I made the backup first of all after unlocking the bootloader and the TVRP firmware. The first time I stitched with Rescue and Smart Assistant https://www.motorola.com/us/rescue-and-smart-assistant/p. I think that this program knows exactly what firmware I need. But it did not help In the off state, the device responds normally to the cable (it charges, connects to the PC where all the drivers are installed, I flashed it many times and tried various factory firmware) but if you connect the cable after the logo image (logo.bin) , until you reboot the device with the cable connected and if you turn it off. That is, when the android system is loaded, the device stubbornly does not want to see the connection. I think that the problem is not in the hardware type because with the firmware I would get a bunch of errors or just could not connect the device but everything works

Smartphone Killer said:
Thank you. I know about all this. I made the backup first of all after unlocking the bootloader and the TVRP firmware. The first time I stitched with Rescue and Smart Assistant https://www.motorola.com/us/rescue-and-smart-assistant/p. I think that this program knows exactly what firmware I need. But it did not help In the off state, the device responds normally to the cable (it charges, connects to the PC where all the drivers are installed, I flashed it many times and tried various factory firmware) but if you connect the cable after the logo image (logo.bin) , until you reboot the device with the cable connected and if you turn it off. That is, when the android system is loaded, the device stubbornly does not want to see the connection. I think that the problem is not in the hardware type because with the firmware I would get a bunch of errors or just could not connect the device but everything works
Click to expand...
Click to collapse
Like I said - if you flashed stock firmware exactly like I posted above with the latest retail firmware from the site in the link and you still have issues it's a hardware problem - either the board or the USB cable you are using