Database Develop

How to re-lock XT1925-6 on firmware ALI_RETAIL_8.0.0_OPS27.104-15-10-4

With firmware ALI_RETAIL_8.0.0_OPS27.104-15-10-4 rooted enable adb and unlock oem boot loader in the system settings,
reboot in fastboot mode and run:
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 dspso.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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot and run this command ONE BY ONE and wait for each one to finish before adding the next one
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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot oem fb_mode_clear

xjunior said:
I'm trying to re-lock my bootloader, but nothing works
Always get a boot loader not signed error and bad key ,
Did anybody relocked this specific model?
I've tried this method and a few others with different firmware and bat file and individually flashing the commands
Click to expand...
Click to collapse
Just saying if you trying to relock the bootloader to send it into moto you can't. The second you request your unlock key it voids the warranty and flags your device for there repair department.

I've figure out
With firmware ALI_RETAIL_8.0.0_OPS27.104-15-10-4 rooted enable adb and unlock oem boot loader in the system settings,
reboot in fastboot mode and run:
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 dspso.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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot and run this command ONE BY ONE and wait for each one to finish before adding the next one
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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot oem fb_mode_clear

Will this bring back the video calling option? I have the same device

HELP! INFOImage signed with key bad key (Moto G6 xt-1922-3) Can't flash stock rom.

HI, i need your help!
I bricked my phone, i could only see a black screen.
I have managed to get around that by flashing the bootloader back.
Now my phone only boots into bootloader no matter what.
The reason is, when i try to flash a stock rom i get the message (INFOImage signed with key bad key) on almost every .img
I've tried downloading the regions that seemed to be mine but they don't work. RETAIL, RETEU, TELEU, VIPEU and so on...
My phone was brought from T-Mobile. it is the xt-1922-3 variant.
AND YES, the bootloader is unlocked. (i've also managed to flash some sort of stock recovery because twrp wouldn't work, because i can't tap the screen)

I have the same problem. How do I solve it?

@Alyctro
DUDE, YOU HAVE A MOTO G6 PLAY.
Try the RETAIL firmware listed here:
https://mirrors.lolinet.com/firmware/moto/aljeter/official/
If you're trying to relock the bootloader, which should fix the "bad key" message, follow this:
Code:
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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
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 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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
Otherwise, this should work, but you'll still get "bad key" message when flashing boot.img and recovery.img (this is due to the bootloader being unlocked):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot

Ragarianok said:
@Alyctro
DUDE, YOU HAVE A MOTO G6 PLAY.
Try the RETAIL firmware listed here:
https://mirrors.lolinet.com/firmware/moto/aljeter/official/
If you're trying to relock the bootloader, which should fix the "bad key" message, follow this:
Code:
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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
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 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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
Otherwise, this should work, but you'll still get "bad key" message when flashing boot.img and recovery.img (this is due to the bootloader being unlocked):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
i need help too. it says image signed with bad key when flashing bootloader.img. i have a retus moto g6. any help is appreciated

Ragarianok said:
@Alyctro
DUDE, YOU HAVE A MOTO G6 PLAY.
Try the RETAIL firmware listed here:
https://mirrors.lolinet.com/firmware/moto/aljeter/official/
If you're trying to relock the bootloader, which should fix the "bad key" message, follow this:
Code:
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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
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 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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
Otherwise, this should work, but you'll still get "bad key" message when flashing boot.img and recovery.img (this is due to the bootloader being unlocked):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
@Ragarianok
Perfect, it works, moto g 6 play XT1922-5_ALJETER, thanks.

Guide: restore River to good as new stock, clean bootloader

Edit: i just realized I put this in the wrong area, can a mod help me out
This took me hours to figure out honestly, and I have experience with this stuff. So, I want this to be as easy to find as possible for other folks.
To go back to stock:
1. Hold down Power and Volume till the boot menu shows up.
2. Plug the phone into your PC
3. Get the newest firmware for your phone model. I bought mine at Best Buy, so it was RETUS aka retail US. https://mirrors.lolinet.com/firmware...iver/official/
4. Extract the archive, and enter that folder in your terminal
5. Run the following commands from that folder. I saved these commands in a shell script and ran it but I think you can just paste it
THIS WILL WIPE ANY DATA ON YOUR PHONE AND PUT IT BACK TO FULL FACTORY FIRMWARE WITH LOCKED BOOT LOADER. At least when I ran it, it got my phone 100% no more complaints when it boots about untrusted code. This also restored my OTA ability and I was able to get the Android 10 update without any issues.
fastboot oem lock begin
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 dtbo dtbo.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 system system.img_sparsechunk.10
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot oem lock
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 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 system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot oem lock
Click to expand...
Click to collapse

idumych said:
Edit: i just realized I put this in the wrong area, can a mod help me out
Click to expand...
Click to collapse
[Using "Report" button] How to Report issues / Moderators assistance by TonyStark
https://forum.xda-developers.com/showthread.php?t=1718423
Sent from my ali using XDA Labs

XT1965-3 Can't load Android system

Hello,
I have a Moto G 7 Plus (a XT1965-3 EU), which I softbricked when aborting an Android update by mistake (power button hold in bag while updating....)
I'm stuck on Android recovery with the message
Code:
Can't load Android system. Your data may be corrupt
. I have two options, Try again or Factory data reset (not an acceptable option).
What I tried so far:
- I tried this tutorial, but Motorola doesn't release the images, and sideloading this image (LAKE_RETAIL_9.0_PPWS29.98-111-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), gives me this message :
Code:
footer is wrong
Signature verification failed
error: 21
- I tried to call the Motorola support, but they won't give me the OTA image, nor help me in a useful way.
- I wanted to install a custom recovery, but unlocking the oem would wipe everything, so no thanks.
I would rather get all the data than repairing the phone (I got it for free thanks to an Amazon Prime trial...), I have several priceless souvenirs in it, and of course I lost my backup drive when I moved away.
Thank you in advance for your help

NicolasBFR said:
Hello,
I have a Moto G 7 Plus (a XT1965-3 EU), which I softbricked when aborting an Android update by mistake (power button hold in bag while updating....)
I'm stuck on Android recovery with the message
Code:
Can't load Android system. Your data may be corrupt
. I have two options, Try again or Factory data reset (not an acceptable option).
What I tried so far:
- I tried this tutorial, but Motorola doesn't release the images, and
Click to expand...
Click to collapse
I don't know if these still work.
Update Tools
[TOOL][WIN] OTA Updates (Motorola)
[TOOL] Motorola OTA Link Generator Tool
NicolasBFR said:
sideloading this image (LAKE_RETAIL_9.0_PPWS29.98-111-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), gives me this message :
Code:
footer is wrong
Signature verification failed
error: 21
Click to expand...
Click to collapse
That image is not an OTA, it's the full firmware and is not coded for installing with recovery, it's meant for fastboot mode.
You can try flashing with fastboot.exe
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

sd_shadow said:
I don't know if these still work.
Update Tools
[TOOL][WIN] OTA Updates (Motorola)
[TOOL] Motorola OTA Link Generator Tool
Click to expand...
Click to collapse
Unfortunatly, both require ro.build.version.full to get the appropriate OTA image, and my device won't give it to me with fastboot getvar all . Any idea how I could find it ?
As for Fastboot flash, I would loose the data, which is not an option.

NicolasBFR said:
As for Fastboot flash, I would loose the data, which is not an option.
Click to expand...
Click to collapse
No, only if you use fastboot erase userdata

sd_shadow said:
No, only if you use fastboot erase userdata
Click to expand...
Click to collapse
So, I just have to do fastboot flash with all the .img and sparsechunk files (even though my bootloader is not unlocked and the device not rooted) ?
Why do all internet tutorials erase both cache and userdata ?
And what is the worse that could happen ?
I attached a screen of the archive content:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

NicolasBFR said:
So, I just have to do fastboot flash with all the .img and sparsechunk files (even though my bootloader is not unlocked and the device not rooted) ?
Why do all internet tutorials erase both cache and userdata ?
And what is the worse that could happen ?
I attached a screen of the archive content:
View attachment 5421721
Click to expand...
Click to collapse
Flashing with a locked bootloader is tricky.
Your best option is using RSD Lite with an old Windows 7 or XP Machine
The servicefile.xml and the flashfile.xml contain the flash commands
the servicefile shouldn't have the userdata line, the flashfile does.
Use Notepad++ to remove the userdata line and save, then flash with RSD Lite.
If that is not an option you can try fastboot.exe
Use the servicefile.xml and the Online FlashFile Converter
run the commands one at a time, if you get an error stop.
and see my Troubleshooting

sd_shadow said:
If that is not an option you can try fastboot.exe
Use the servicefile.xml and the Online FlashFile Converter
run the commands one at a time, if you get an error stop.
and see my Troubleshooting
Click to expand...
Click to collapse
I had USB 3.0 ports so I had the "(bootloader) is-logical:partiti : not found" error.
if you want to know my script (from Online Flashfile converter), is
Bash:
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 dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
# fastboot erase carrier
# fastboot erase ddr
fastboot oem fb_mode_clear
echo English - Process concluded!
pause
fastboot reboot
exit
I have a second computer from 2005 with 2.0 USB, I am going to try again in few hours.
Also, all my computers are on Arch Linux (Manjaro) and I download fastboot with pacman,
fastboot --version returns me
Bash:
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
.
Is my fastboot version ok ?

I am so stupid, I ran the commands above using my old computer, the same fastboot version and with a USB 2.0 port, but with once in a shell script. I don't even have the logs, and now the "Can't load android system" doesn't even appear anymore ! It's just a bootloop.
What should I do ?

Okay @sd_shadow , I used the linux mfastboot recommended by your guides, and this time it managed to flash everything... but I'm back to the bootloader error menu "Can't load Android system"...
Maybe I could flash TWRP recovery (or even just fastboot boot ?), then use it to retrieve userdata and then factory reset ?
EDIT: I tried fastboot boot TWRP.img but I got "permission denied". Maybe there is a custom ROM out there that don't need the userdata ?

Bootloop with Motorola Logo

Well, I'll tell you ... Well, I bought a Moto G5S Plus for that of late 2018, everything worked fine within normal, sometimes when I restarted it, there were some System errors that did not respond to which I did not pay much attention, because then it worked normal ... until the beginning of this year, the memory was a little full, so I inserted a Micro SD to free up some space and move many images that I had there. I turned it off to insert the SD and when I went to turn it on, it did not pass the Motorola Logo. I thought it was on drums or something, I reset it, did various things to it and to this day, it continues like this ...
In the first instance, not knowing much or nothing about the topic, try this:
Unsuccessfully, then I also tried clearing the cache via Fastboot, but also had no solution ...
Then there was the Hard Reset through Fastboot or reinstalling the Rom through AVOID, because I have many documents, especially Notepads with important information, as well as contacts and multimedia material that I need to recover ...
So I decided to keep looking and luckily I found an interesting post in this forum:
https://www.htcmania.com/showthread....1543&styleid=6
This gave me hope again, besides that I am lucky to have a Moto G2, so I tried the steps described in that post ... And I realized that it obviously works, it does not erase the data from the computer ... Then I proceeded to do it with the Moto G5S Plus and some commands did not work, I did a little research and realized that the files of each ROM were totally different, so I found some specific commands for the Moto G5S Plus:
(Downloading this rom: SANDERS_RETAIL_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
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 system system.img_sparsechunk.10
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
I also found another version of commands that differs a bit
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 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 system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
In that case, following the instructions in the aforementioned post,
(https://www.htcmania.com/showthread....1543&styleid=6), I decided to take into account the recommendations and AVOID commands such as:
fastboot flash partition gpt.bin
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Everything that could erase data, but I also had doubts about these, I don't know what action they perform:
fastboot flash partition gpt.bin
fastboot oem fb_mode_set
fastboot erase DDR
fastboot oem fb_mode_clear
Finally, I decided to just use these commands, but the phone remained the same in the Logo Bootloop:
fastboot devices
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 system system.img_sparsechunk.10
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
It is here, when I ****ing turn to experts like you, since I don't know what else to do and I still have many doubts ... Do you think that data has been deleted with these procedures or is everything still the same? Is there a way to install the TWRP to save data?
Many videos and forums that I have read say that it can also be BATTERY FAILURE, but I very much doubt that it is, in addition to removing the battery from this model, yes I'm not bad I think you have to remove the display and well, many technicians do not know Buy for it ... Also normal charge when I charge it to full and the battery is consumed in the normal percentage, so that's why I don't think ... But I do need that if they are so kind to give me a hand, because I no longer know What else to do, I really sometimes make my head a madhouse with this topic ...
Friends I thank you and I am very aware. Really thank you very much

Help me!! PLEASE!!