Database Develop

No OS, adb: Total xfer=0.00x

Hi everyone.
Accidentally wiped the OS, apparently people fixed it using ADB. I'm trying to sideload a rom but adb says "Total xfer 0.00x" and my moto g says ADB Sideload Complete: Failed.
Any ideas how to fix this?
ADDED:
In case if someone wonders how I fixed this:
1) Reboot the phone into bootloader mode.
2) Open a command prompt / terminal (Start -> cmd.exe in Win7) and browse to the folder with the extracted firmware.
3) Connect your phone to your PC.
4) Flash stock firmware.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot -w

some commands can not load
and no know such device:silly:

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.

cant flash oreo sign Firmware/cant write boot.img (no error)

Hello,
I get always the same error for every thing I try to flash " cant write ...... ((no error))
The device have Android 9 stock firmware unsigned security update november 2018
And I try to install PAYTON_OPWS27.57_40_14_XT1900_7_DS_8.0.0_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
bootloader is open fastboot run,
Flashing works with this pc and OS normaly
since I try to flash my smartfone I have noch basband anymore.
I used this file
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 flash modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.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_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
PAUSE
fastboot reboot

so you're trying to downgrade from pie to oreo. is the bootloader unlocked?

yes , but the first time I try to flash I forgot it , after that I unlocked the device and I try it again and I have the same error message

Flash just the bootloader "fastboot flash bootloader bootloader.img", then press volume-down multiple times until you see "Log". What is the output?
It might be related to these issues (thread 1, thread 2). Workarounds include using another PC or older version of fastboot.

I try it today , you mean the bootloader from Oreo right?
thanks for support

flashing bootloader was sucessful
here is the log:
cmd:getvar:slot-count
cmd:gevar:has-slot:bootloader
cmd:getvarartiton-type:bootloader
Cmd: getvar:maxdownload-size
cmd: download:0094c100
cmd: flash:bootloader
I try to flash all again it stop at dsp dspo.bin
the status change to official baseband is back but I stilll have android 9

tomtom_38 said:
I try to flash all again it stop at dsp dspo.bin
Click to expand...
Click to collapse
Try flashing again, this time one-by-one. Attach the bootloader log when it stops at dsp.
On the PC side, did flashing dsp resulted in "cant write ...... ((no error))" error. What are the command outputs?

C:\Users\Thomas\Desktop\minimal_adb_fastboot_1.4.3_portable_XT1900>fastboot flash dsp dspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
this happens by flashing dsp dspso
and this ist the log
flashing bootloader was sucessful
here is the log:
cmd:getvar:slot-count
cmd:getvar:slot-count
cmd: getvar:has slot:bluetooth
cmd: getvar:current-slot
cmd:getvarartition-type:bluetooth_a
cmd:getvar:max-download-size
cmd:download:0046f100
cmd:flash:bluetooth_a
cmd:getvar:slot-count
cmd:getvar:has-slot:dsp
cmd:getvar:current-slot
cmd:getvarartiton-type:dsp_a
cmd:getvar:max-download-size
cmd:download:01000000
Cmd: getvar:maxdownload-size
cmd: download:0094c100
cmd: flash:bootloader
this makes me perplex
Im erasing modem st1 but Iam not write everything
-------------------------------------------
C:\Users\Thomas\Desktop\minimal_adb_fastboot_1.4.3_portable_XT1900>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
------------------------------------------------------------------------------------------------------------------
C:\Users\Thomas\Desktop\minimal_adb_fastboot_1.4.3_portable_XT1900>fastboot flash modemst2
unknown partition 'modemst2'
error: cannot determine image filename for 'modemst2'

tomtom_38 said:
>fastboot flash modemst2
unknown partition 'modemst2'
error: cannot determine image filename for 'modemst2'
Click to expand...
Click to collapse
The script you got is incorrect. modemst2 should be erased instead.
I couldn't find the version you have from the mirror. I found another OPWS27.57 zip.
They're both "OPWS27.57" and Android 8.0, so the script should be similar.
If you want to make sure, inspect line 14 onward of the flashfile.xml. Check whether the zip has recovery.img as well.
Unzip the attached file. Put the attached flash_all.bat into the firmware folder and run it.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 8
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 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_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot-bootloader
sleep 8

ok, it worked with clean win 7 .
thanks, but
in no firmware is a recovery .img and I cant do an ota update to pie.

tomtom_38 said:
in no firmware is a recovery .img and I cant do an ota update to pie.
Click to expand...
Click to collapse
If you did "fastboot flash boot boot.img", the stock recovery should be there.
munchy_cool said:
flash stock boot.img.
recovery is built within boot.img.
Click to expand...
Click to collapse
-------------------
Try this guide. But I'm puzzled why you downgrade to Oreo and back to Pie.
btw, "bootloader is open fastboot run" is mentioned in the OP, is the bootloader unlocked?

I will try it,
I do it because I need a official signed version to send my smartpfone to a repair center.
the best sigened version I found is oreo and I downgrade to oreo and upgtade with motrola update services to pie

hey I flashed slot a and b with the same firmware but the message "you loading a different os" still apear.
The bootloader show that the firmware is a official version?! I looking for a solution but I found only the way tto flash both slots

What commands did you use to flash to both slots?
They should be:
fastboot --set-active=a
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_b system_other.img

Ok I use this comand to change the slot
fastboot --set-active=other
and then I flash manually all positions from the flash _all .zip from the first page
one time for each slot

tomtom_38 said:
hey I flashed slot a and b with the same firmware but the message "you loading a different os" still apear.
Click to expand...
Click to collapse
Does it look like this?
tomtom_38 said:
The bootloader show that the firmware is a official version
Click to expand...
Click to collapse
I'm using Havoc and it also shows as "official".
tomtom_38 said:
fastboot --set-active=other
Click to expand...
Click to collapse
you mean "fastboot --set-active=b"?

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!!