Help for Motorola XT1672 - Moto G5 Questions & Answers

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

Related

[HARDBRICKED] PLZ Help Me Give Me Solution

I need help to recover my moto g5
Do you mean soft bricked
Hard bricked means you can't get into bootloader mode
Soft bricked means the phone doesn't boot but you can still get into bootloader mode
If you are hard bricked you need specialist hardware or a new motherboard
If you are softbricked either
If you have an unlocked bootloader
Go into bootloader mode - Flash twrp via fastboot (instructions on twrp thread) and then wipe system data cache & flash a custom rom
If you don't have an unlocked bootloader or don't want a custom rom
Go into bootloader mode
Flash stock firmware via fastboot (Google for firmware)
Are you sure about hardbrick?
As @TheFixItMan said, you are probably soft bricked. If you ARE truly hard bricked then tough luck. Get your stock firmware here. Flash it using fastboot. Here are the commands, if you don't know them.
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 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
Cheers:good:

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

Bricked XT1922-3. Need help :(

Hi, I have bricked my phone when I tried to flash my stockboot en recovery img files. What happens is that everytime I reboot the phone, it automatically reboots to the bootloader. I can access twrp.
I tried to flash stock firmware myself, but I flashed XT1921-3 instead of XT1922-3 because I couldnt find the right version. Nothing changed. I also tried to flash a GSI ROM and nothing changes there as well. Can someone help me out?
I managed to get my hands
You will have to pass the last stock in 9.0 for your G6 play, I did it in mine and I go back I was with an equal problem
i am used this version for my cellphone XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25_cid50_subsidy-DEFAULT_regulatory-XT1922-5-BRAZIL-MANAUS_CFC you used similar version
in fastboot my solucion
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 dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 vendor vendor.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Worked like a charm for my Xt1922-3 RETEU.

Problems relocking bootloader on Moto G5S

After running into some issues with my custom ROM, I decided to flash back the Stock firmware on my Moto G5S. In that process I also tried to relock my bootloader but I ran into some issues that I couldnt find an answer to on the Internet.
The first issue was that I couldnt flash the gpt.bin (not exactly sure what it is) and got the error message that it was a downgrade which wasnt possible. The flashing of the other files went without problems at all and also the phone booted sucessfully. So does that gpt.bin matter when flashing the Stock Rom or can I just ignore it?
I doubt that because when I try to run oem lock it gives back an error and says that I had to check "Allow OEM-Unlock" in Developer settings which isn't possible because obviously the bootloader is already unlocked and so it is greyed out.
So what did I do wrong and how do I lock my bootloader again?
DOWNLOAD OREO ROM AND TRY THIS
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 system system.img_sparsechunk.9
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 oem lock
fastboot oem lock
fastboot reboot
That is basically what i already tried except of the two lines erase customize and erase clogo. But I'm getting permission denied errors with these and my bootloader still wont lock.
Is there any way to widen the permissions you have in the bootloader?

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

Categories

Resources