[Fix] Motorola_XML_To_Batch_Script - Moto G7 Power Guides, News, & Discussion

If your output looks like this do the following.
Code:
sending 'modema' (65420 KB)...
OKAY [ 1.495s]
writing 'modema'...
(bootloader) Invalid partition name modema
FAILED (remote failure)
finished. total time: 1.525s
target reported max download size of 536870912 bytes
sending 'fsga' (9192 KB)...
OKAY [ 0.213s]
writing 'fsga'...
(bootloader) Invalid partition name fsga
FAILED (remote failure)
finished. total time: 0.232s
target reported max download size of 536870912 bytes
sending 'dspa' (16384 KB)...
OKAY [ 0.378s]
writing 'dspa'...
(bootloader) Invalid partition name dspa
FAILED (remote failure)
finished. total time: 0.393s
target reported max download size of 536870912 bytes
sending 'logoa' (1285 KB)...
OKAY [ 0.034s]
writing 'logoa'...
(bootloader) Invalid partition name logoa
FAILED (remote failure)
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'boota' (32768 KB)...
OKAY [ 0.820s]
writing 'boota'...
(bootloader) Invalid partition name boota
FAILED (remote failure)
finished. total time: 0.834s
You need to specify the A/B partitions like the following. Just add "_" to the Invalid partition name.
Code:
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_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_a 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_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg_a fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit

Related

[GUIDE] Moto G7 Power/Supra [All Versions] Flash Back to Stock Firmware

Broke your G7 Power? No worries! As long as you can still get to fastboot, you can fix it. Note that this WILL wipe all data on the phone!
First download the stock firmware for your model here:
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Then download the Android Platform Tools, here:
Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Extract the firmware files to a folder on your desktop, then extract your Android Platform Tools to the same folder.
Get your phone into fastboot mode, connect it to your computer, shift+right click (on Windows) in your working folder and open Powershell (on mac and linux, open a terminal and cd to your working folder).
Run these commands (these are formatted for Powershell. Just remove the "./" for other platforms), you can just copy+paste the whole thing into powershell and run them all at once.
Code:
./fastboot oem fb_mode_set
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash modem_a NON-HLOS.bin
./fastboot flash fsg_a fsg.mbn
./fastboot erase modemst1
./fastboot erase modemst2
./fastboot flash dsp_a adspso.bin
./fastboot flash logo_a logo.bin
./fastboot flash boot_a boot.img
./fastboot flash dtbo_a dtbo.img
./fastboot flash system_a system.img_sparsechunk.0
./fastboot flash system_a system.img_sparsechunk.1
./fastboot flash system_a system.img_sparsechunk.2
./fastboot flash system_a system.img_sparsechunk.3
./fastboot flash system_a system.img_sparsechunk.4
./fastboot flash system_a system.img_sparsechunk.5
./fastboot flash system_a system.img_sparsechunk.6
./fastboot flash system_a system.img_sparsechunk.7
./fastboot flash system_a system.img_sparsechunk.8
./fastboot flash system_a system.img_sparsechunk.9
./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_a vendor.img_sparsechunk.0
./fastboot flash vendor_a vendor.img_sparsechunk.1
./fastboot flash oem_a oem.img
./fastboot flash oem_b oem_other.img
./fastboot erase userdata
./fastboot erase DDR
./fastboot oem fb_mode_clear
./fastboot reboot
The phone will reboot, and you're done! Hopefully you'll be back to stock (although this wont re-lock your bootloader and restore your warranty), and you can try rooting/flashing/whatever again.
Can I flash any rom xt1955? I can't find my stock firmware claro colombia
Poto222 said:
Can I flash any rom xt1955? I can't find my stock firmware claro colombia
Click to expand...
Click to collapse
I have been able to flash the RETUS firmware on my LATAM without any issue.
I am concerned about this piece of comands
./fastboot erase modemst1
./fastboot erase modemst2
As I don't see any flash of those partitions, by chance, it doesn't have imei of GPS data?
fastboot oem fb_mode_set fastboot flash partition gpt.bin fastboot flash bootloader bootloader.img fastboot flash modem_a NON-HLOS.bin fastboot flash fsg_a fsg.mbn fastboot erase modemst1 fastboot erase modemst2 fastboot flash dsp_a adspso.bin fastboot flash logo_a logo.bin fastboot flash boot_a boot.img fastboot flash dtbo_a dtbo.img fastboot flash system_a system.img_sparsechunk.0 fastboot flash system_a system.img_sparsechunk.1 fastboot flash system_a system.img_sparsechunk.2 fastboot flash system_a system.img_sparsechunk.3 fastboot flash system_a system.img_sparsechunk.4 fastboot flash system_a system.img_sparsechunk.5 fastboot flash system_a system.img_sparsechunk.6 fastboot flash system_a system.img_sparsechunk.7 fastboot flash system_a system.img_sparsechunk.8 fastboot flash system_a system.img_sparsechunk.9 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_a vendor.img_sparsechunk.0 fastboot flash vendor_a vendor.img_sparsechunk.1 fastboot flash oem_a oem.img fastboot flash oem_b oem_other.img fastboot erase userdata fastboot erase DDR fastboot oem fb_mode_clear fastboot reboot
^deleted ./
I have the US unlocked model from Best Buy. Should I be able to flash the VZW firmware to potentially allow their WIFI calling?
I get this error when i try reflashing. Here are logs. Any help is appreciated.
PS C:\adb> ./fastboot oem fb_mode_set
>> ./fastboot flash partition gpt.bin
>> ./fastboot flash bootloader bootloader.img
>> ./fastboot flash modem_a NON-HLOS.bin
>> ./fastboot flash fsg_a fsg.mbn
>> ./fastboot erase modemst1
>> ./fastboot erase modemst2
>> ./fastboot flash dsp_a adspso.bin
>> ./fastboot flash logo_a logo.bin
>> ./fastboot flash boot_a boot.img
>> ./fastboot flash dtbo_a dtbo.img
>> ./fastboot flash system_a system.img_sparsechunk.0
>> ./fastboot flash system_a system.img_sparsechunk.1
>> ./fastboot flash system_a system.img_sparsechunk.2
>> ./fastboot flash system_a system.img_sparsechunk.3
>> ./fastboot flash system_a system.img_sparsechunk.4
>> ./fastboot flash system_a system.img_sparsechunk.5
>> ./fastboot flash system_a system.img_sparsechunk.6
>> ./fastboot flash system_a system.img_sparsechunk.7
>> ./fastboot flash system_a system.img_sparsechunk.8
>> ./fastboot flash system_a system.img_sparsechunk.9
>> ./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_a vendor.img_sparsechunk.0
>> ./fastboot flash vendor_a vendor.img_sparsechunk.1
>> ./fastboot flash oem_a oem.img
>> ./fastboot flash oem_b oem_other.img
>> ./fastboot erase userdata
>> ./fastboot erase DDR
>> ./fastboot oem fb_mode_clear
>> ./fastboot reboot
...
OKAY [ 0.002s]
finished. total time: 0.002s
error: cannot open 'gpt.bin'
error: cannot open 'bootloader.img'
error: cannot open 'NON-HLOS.bin'
error: cannot open 'fsg.mbn'
erasing 'modemst1'...
OKAY [ 0.018s]
finished. total time: 0.018s
erasing 'modemst2'...
OKAY [ 0.018s]
finished. total time: 0.018s
error: cannot open 'adspso.bin'
error: cannot open 'logo.bin'
error: cannot open 'boot.img'
error: cannot open 'dtbo.img'
error: cannot open 'system.img_sparsechunk.0'
error: cannot open 'system.img_sparsechunk.1'
error: cannot open 'system.img_sparsechunk.2'
error: cannot open 'system.img_sparsechunk.3'
error: cannot open 'system.img_sparsechunk.4'
error: cannot open 'system.img_sparsechunk.5'
error: cannot open 'system.img_sparsechunk.6'
error: cannot open 'system.img_sparsechunk.7'
error: cannot open 'system.img_sparsechunk.8'
error: cannot open 'system.img_sparsechunk.9'
error: cannot open 'system_b.img_sparsechunk.0'
error: cannot open 'system_b.img_sparsechunk.1'
error: cannot open 'system_b.img_sparsechunk.2'
error: cannot open 'vendor.img_sparsechunk.0'
error: cannot open 'vendor.img_sparsechunk.1'
error: cannot open 'oem.img'
error: cannot open 'oem_other.img'
erasing 'userdata'...
OKAY [ 0.286s]
finished. total time: 0.286s
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.001s
...
OKAY [ 0.002s]
finished. total time: 0.002s
rebooting...
finished. total time: 0.001s
Idiyeet said:
I get this error when i try reflashing. Here are logs. Any help is appreciated.
PS C:\adb> ./fastboot oem fb_mode_set
>> ./fastboot flash partition gpt.bin
>> ./fastboot flash bootloader bootloader.img
>> ./fastboot flash modem_a NON-HLOS.bin
>> ./fastboot flash fsg_a fsg.mbn
>> ./fastboot erase modemst1
>> ./fastboot erase modemst2
>> ./fastboot flash dsp_a adspso.bin
>> ./fastboot flash logo_a logo.bin
>> ./fastboot flash boot_a boot.img
>> ./fastboot flash dtbo_a dtbo.img
>> ./fastboot flash system_a system.img_sparsechunk.0
>> ./fastboot flash system_a system.img_sparsechunk.1
>> ./fastboot flash system_a system.img_sparsechunk.2
>> ./fastboot flash system_a system.img_sparsechunk.3
>> ./fastboot flash system_a system.img_sparsechunk.4
>> ./fastboot flash system_a system.img_sparsechunk.5
>> ./fastboot flash system_a system.img_sparsechunk.6
>> ./fastboot flash system_a system.img_sparsechunk.7
>> ./fastboot flash system_a system.img_sparsechunk.8
>> ./fastboot flash system_a system.img_sparsechunk.9
>> ./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_a vendor.img_sparsechunk.0
>> ./fastboot flash vendor_a vendor.img_sparsechunk.1
>> ./fastboot flash oem_a oem.img
>> ./fastboot flash oem_b oem_other.img
>> ./fastboot erase userdata
>> ./fastboot erase DDR
>> ./fastboot oem fb_mode_clear
>> ./fastboot reboot
...
OKAY [ 0.002s]
finished. total time: 0.002s
error: cannot open 'gpt.bin'
error: cannot open 'bootloader.img'
error: cannot open 'NON-HLOS.bin'
error: cannot open 'fsg.mbn'
erasing 'modemst1'...
OKAY [ 0.018s]
finished. total time: 0.018s
erasing 'modemst2'...
OKAY [ 0.018s]
finished. total time: 0.018s
error: cannot open 'adspso.bin'
error: cannot open 'logo.bin'
error: cannot open 'boot.img'
error: cannot open 'dtbo.img'
error: cannot open 'system.img_sparsechunk.0'
error: cannot open 'system.img_sparsechunk.1'
error: cannot open 'system.img_sparsechunk.2'
error: cannot open 'system.img_sparsechunk.3'
error: cannot open 'system.img_sparsechunk.4'
error: cannot open 'system.img_sparsechunk.5'
error: cannot open 'system.img_sparsechunk.6'
error: cannot open 'system.img_sparsechunk.7'
error: cannot open 'system.img_sparsechunk.8'
error: cannot open 'system.img_sparsechunk.9'
error: cannot open 'system_b.img_sparsechunk.0'
error: cannot open 'system_b.img_sparsechunk.1'
error: cannot open 'system_b.img_sparsechunk.2'
error: cannot open 'vendor.img_sparsechunk.0'
error: cannot open 'vendor.img_sparsechunk.1'
error: cannot open 'oem.img'
error: cannot open 'oem_other.img'
erasing 'userdata'...
OKAY [ 0.286s]
finished. total time: 0.286s
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.001s
...
OKAY [ 0.002s]
finished. total time: 0.002s
rebooting...
finished. total time: 0.001s
Click to expand...
Click to collapse
Are the img files in the same folder as the one you are using fastboot in?
I got my issue fixed. Thanks! Just had to restore my font through the app. Thankfully it had the default one for my Moto G7 Power. But thank you for the help. And yes, they were in the same folder
diversenerd said:
Broke your G7 Power? No worries! As long as you can still get to fastboot, you can fix it. Note that this WILL wipe all data on the phone!
First download the stock firmware for your model here:
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Click to expand...
Click to collapse
if only this actually had RETEU2 images...
Does flashing the full firmware completely wipe the system side of the phone? I installed a Magisk module that has seemed to mess up my sim card stability (continuously flashed in and out) but I think there's still something from that module causing issues. I tried a full firmware flash but the problem persists. I have tried the sim card in another device and don't have the same problem, so I ruled out it being the actual sim.
Just kinda stuck right now and don't know what to do.
So, I'm looking for any ideas at this point. I have an xt1955-5 that now has no baseband, no esn, no signal at all. It's fully functioning otherwise. I've reflashed stock firmware (multiple times), but nothing seems to help. And it's not the sim card, because I'm currently using it in a back up phone. Just looking for any suggestion to try.
CCivale said:
Does flashing the full firmware completely wipe the system side of the phone? I installed a Magisk module that has seemed to mess up my sim card stability (continuously flashed in and out) but I think there's still something from that module causing issues. I tried a full firmware flash but the problem persists. I have tried the sim card in another device and don't have the same problem, so I ruled out it being the actual sim.
Just kinda stuck right now and don't know what to do.
Click to expand...
Click to collapse
Take it to guarantee, that's already a factory fault.
Flashing the retus firmware gave my phone a performance boost with no carrier bloatware. My icon now says LTE instead of 4g/LTE. I'm on metro by TMobile. I took out my sim untill the phone booted up after flashing via fastboot.
Thanks again for this thread. Awesome phone.!!!!!
do u still have wifi calling on Metro with the RETUS firmware?? if so which RETUS did u use the 1st or 2nd in the list
jhjhjhjhjhjh said:
Flashing the retus firmware gave my phone a performance boost with no carrier bloatware. My icon now says LTE instead of 4g/LTE. I'm on metro by TMobile. I took out my sim untill the phone booted up after flashing via fastboot.
Thanks again for this thread. Awesome phone.!!!!!
Click to expand...
Click to collapse
hofs1 said:
do u still have wifi calling on Metro with the RETUS firmware?? if so which RETUS did u use the 1st or 2nd in the list
Click to expand...
Click to collapse
Yes wifi calling works. 5gz wifi works. I used the 2nd one in the list. .
BTW These are the correct Fastboot command that should be in main post. For a normal firmware flash.
You don't have to type system_a or whatever_a because it will flash to partition A by default you only need to specify the partition when something need to be flashed on partition B in that case yes you type system_b or whatever_b.
Code:
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_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 oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
And these are the correct fastboot commands to run for a Full successful re-lock.
This time you start with "fastboot oem lock begin" then the normal flashing procedure and at the end after "fastboot oem lock" if everything went well it will lock then you can fastboot reboot if something else needs to be done (Moto are a-holes) it will tell you that you need to flash signed boot.img or flash signed system image to fully lock it. in that case after "fastboot oem lock" just re run the flash system commands only then fastboot oem lock it should lock this time. Good Luck!
Code:
fastboot oem lock begin
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_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 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 reboot
CCivale said:
So, I'm looking for any ideas at this point. I have an xt1955-5 that now has no baseband, no esn, no signal at all. It's fully functioning otherwise. I've reflashed stock firmware (multiple times), but nothing seems to help. And it's not the sim card, because I'm currently using it in a back up phone. Just looking for any suggestion to try.
Click to expand...
Click to collapse
Edit: I was playing around last night with this trying to find a solution for missing baseband/radio/modem after flashing to latest and then trying to go back. Well the thing is that something changed in latest firmware and bootloader was also updated so now downgrading brakes the modem. The solution I find last night is flash latest one make sure you have modem and base-band working correctly You will know it is ok after first boot skip connection to wifi and force mobile data data should come up that how you know. Okay after flashing to latest if you want to flash back to OG just flash the OG firmware as normal just don't flash or run these commands
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
This way you can use any firmware and keep your data connection. Enjoy.
I know what happened there, DO NOT FLASH the oldest/first firmware available in the repository that firmware will remove baseband and everything I test it and same happened to me. Do not panic just flash the latest available and you are good.
I flashed my 1955-2 whole shobang. Works perfectly and yes I do have nfc but no 5ghz wifi
JewsRshady said:
I flashed my 1955-2 whole shobang. Works perfectly and yes I do have nfc but no 5ghz wifi
Click to expand...
Click to collapse
Edited my reply was about something else.
NVM ....

Help 0 imei no wifi no cellular signal

I have the xt1789-04 I updated it to android 9.0 without flashing the modems everything worked fine then did flash all to Oreo and the fhlashed pixel experience ROM witch got me into bootloop so I flash Oreo again and now I have now WiFi no data no imei and I tried flashing twrp but it won’t let me keeps on appearing an error message
I had similar issue and I tried following file and it helped me. below code will erase everything on your phone so proceed with caution.
if you are on fastboot mode, try flashing stock oreo with bothslotflashall.bat file(below code). If you dont have mfastboot, please edit below code with "fastboot" command.
fastboot erase all
mfastboot oem fb_mode_set
mfastboot getvar max-sparse-size
mfastboot flash partition gpt.bin
mfastboot flash bootloader_a bootloader.img
mfastboot flash bootloader_b bootloader.img
mfastboot flash modem_a NON-HLOS.bin
mfastboot flash fsg_a fsg.mbn
mfastboot flash modem_b NON-HLOS.bin
mfastboot flash fsg_b fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth_a BTFM.bin
mfastboot flash dsp_a adspso.bin
mfastboot flash logo_a logo.bin
mfastboot flash boot_a boot.img
mfastboot flash system_a system.img_sparsechunk.0
mfastboot flash system_a system.img_sparsechunk.1
mfastboot flash system_a system.img_sparsechunk.2
mfastboot flash system_a system.img_sparsechunk.3
mfastboot flash system_a system.img_sparsechunk.4
mfastboot flash system_a system.img_sparsechunk.5
mfastboot flash oem_a oem.img
mfastboot flash bluetooth_b BTFM.bin
mfastboot flash dsp_b adspso.bin
mfastboot flash logo_b logo.bin
mfastboot flash boot_b boot.img
mfastboot flash system_b system.img_sparsechunk.0
mfastboot flash system_b system.img_sparsechunk.1
mfastboot flash system_b system.img_sparsechunk.2
mfastboot flash system_b system.img_sparsechunk.3
mfastboot flash system_b system.img_sparsechunk.4
mfastboot flash system_b system.img_sparsechunk.5
mfastboot flash oem_b oem.img
mfastboot erase carrier
mfastboot erase ddr
mfastboot oem fb_mode_clear
mfastboot -w
mfastboot --set-active=other
mfastboot reboot-bootloader
Click to expand...
Click to collapse
Will try it when I get home and will let you know for now thank you
latadswapnil said:
I had similar issue and I tried following file and it helped me. below code will erase everything on your phone so proceed with caution.
if you are on fastboot mode, try flashing stock oreo with bothslotflashall.bat file(below code). If you dont have mfastboot, please edit below code with "fastboot" command.
Click to expand...
Click to collapse
Any risk to run "fastboot erase all"
My baseband "Not Found".
Sent from my LG-LS997 using Tapatalk
cgigate said:
Any risk to run "fastboot erase all"
My baseband "Not Found".
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
erase all will erase all the partitions, I have done this on my XT1789-04 several times and never faced any issue.
But be sure that you have a stock rom to flash.
latadswapnil said:
erase all will erase all the partitions, I have done this on my XT1789-04 several times and never faced any issue.
But be sure that you have a stock rom to flash.
Click to expand...
Click to collapse
Actually. the "erase all" does very little things, I wish it can erase the modem_a and modem_b partitions.
>fastboot erase all
erasing 'all'...
(bootloader) erasing ddr ...
(bootloader) erasing carrier ...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing fsc ...
(bootloader) erasing userdata ...
(bootloader) erasing fsg_a ...
(bootloader) erasing fsg_b ...
OKAY [ 0.829s]
finished. total time: 0.830s
cgigate said:
Actually. the "erase all" does very little things, I wish it can erase the modem_a and modem_b partitions.
>fastboot erase all
erasing 'all'...
(bootloader) erasing ddr ...
(bootloader) erasing carrier ...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing fsc ...
(bootloader) erasing userdata ...
(bootloader) erasing fsg_a ...
(bootloader) erasing fsg_b ...
OKAY [ 0.829s]
finished. total time: 0.830s
Click to expand...
Click to collapse
Yeah it doesn't, I dont understand why cant we able to format these system partitions, I thought of blankflashing older bootloader and install older stock rom but my phone doesnt go in EDL mode.
latadswapnil said:
Yeah it doesn't, I dont understand why cant we able to format these system partitions, I thought of blankflashing older bootloader and install older stock rom but my phone doesnt go in EDL mode.
Click to expand...
Click to collapse
Actually, it is very easy to get in EDL mode.
cgigate said:
Actually, it is very easy to get in EDL mode.
Click to expand...
Click to collapse
I tried all the methods available online such as "adl reboot edl" or from twrp nothing works. Phone just reboots normally , once or twice screen went blank but then again system didnt detect the phone and phone rebooted again normally in 30 seconds automatically.
I tried USB 2.0, 3.0, USB C but nothing is working.
latadswapnil said:
I tried all the methods available online such as "adl reboot edl" or from twrp nothing works. Phone just reboots normally , once or twice screen went blank but then again system didnt detect the phone and phone rebooted again normally in 30 seconds automatically.
I tried USB 2.0, 3.0, USB C but nothing is working.
Click to expand...
Click to collapse
"adb reboot edl" works well to get in EDL mode from TWRP.
there is a timing issue
All you needs is to run "flashblanl.bat" in another CMD windows, then immediately issue ""adb reboot edl" command in a CMD windows under twrp,
but my blankflashing can flash, you can see the progress and logs, but it eventually failed, I may need to make another blank flash single image file
gave it a try and it didnt let me flash this is what appeared
quote: C:\Users\gustavo\Downloads\TMO Moto Z2 Force 27.1.5 flashall\TMO Moto Z2 Force 27.1.5 flashall>fastboot erase all
(bootloader) partition-ty: not found
erasing 'all'...
(bootloader) Invalid partition name allrtition-ty
FAILED (remote failure)
finished. total time: 0.023s
i was able to flash the comands but still imei unavailable and no cellular signal and no wifi

moto g5 even after passing software stays on the motorola logo and does not start

Guys I have the G5 that even passing software on it it remains on the motorola logo and does not start in any way to enter fastboot mode needs to be connected to the data cable + the Power buttons and volume less.
Normally just by pressing the combinations the motorolas will enter more this one does not enter and even passing software does not start, any suggestion of what might be?
Model: XT1672
Version ROM: XT1672_CEDRIC_RETBR_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Details:
I took it already so I tested some versions of the rom but only the most current version worked (ran the chambers without errors)
braganetx said:
Guys I have the G5 that even passing software on it it remains on the motorola logo and does not start in any way to enter fastboot mode needs to be connected to the data cable + the Power buttons and volume less.
Normally just by pressing the combinations the motorolas will enter more this one does not enter and even passing software does not start, any suggestion of what might be?
Model: XT1672
Version ROM: XT1672_CEDRIC_RETBR_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Details:
I took it already so I tested some versions of the rom but only the most current version worked (ran the chambers without errors)
Click to expand...
Click to collapse
As long as you get into the bootloader it will be possible to fix - hopefully (When the bootloader is away there are chances too - but that's harder). Can you check the battery? And how did this happen?
nift4 said:
As long as you get into the bootloader it will be possible to fix - hopefully (When the bootloader is away there are chances too - but that's harder). Can you check the battery? And how did this happen?
Click to expand...
Click to collapse
Yes it normally enters fastboot. Give to run all fastboot commands on it, just not ADB because the bootloader is blocked and the usb debugging option is disabled, and as I can't get into the system, then there is no way to activate it. I managed to run the software on it, but even after finishing the commands it does not start.
I don't know exactly what happened, I took this phone only on the Motorola logo.
braganetx said:
Yes it normally enters fastboot. Give to run all fastboot commands on it, just not ADB because the bootloader is blocked and the usb debugging option is disabled, and as I can't get into the system, then there is no way to activate it. I managed to run the software on it, but even after finishing the commands it does not start.
I don't know exactly what happened, I took this phone only on the Motorola logo.
Click to expand...
Click to collapse
Is your bootloader unlocked?
Post the entire cmd output of you trying to flash stock firmware via fastboot
TheFixItMan said:
Is your bootloader unlocked?
Post the entire cmd output of you trying to flash stock firmware via fastboot
Click to expand...
Click to collapse
Ig bootloader is blocked means locked
TheFixItMan said:
Is your bootloader unlocked?
Post the entire cmd output of you trying to flash stock firmware via fastboot
Click to expand...
Click to collapse
Yes, locked bootloader
HTML:
$ fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
$
$ fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
$
$ fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.085s]
finished. total time: 0.104s
$
$ fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.192s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.553s]
finished. total time: 0.745s
$
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (66358 KB)...
OKAY [ 2.296s]
writing 'modem'...
OKAY [ 1.046s]
finished. total time: 3.343s
$
$ fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (2956 KB)...
OKAY [ 0.115s]
writing 'fsg'...
OKAY [ 0.103s]
finished. total time: 0.218s
$
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
$
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
$
$ fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin': No such file or directory
$
$ fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin': No such file or directory
$
$ fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 0.090s]
writing 'logo'...
OKAY [ 0.096s]
finished. total time: 0.187s
$
$ fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.605s]
writing 'boot'...
OKAY [ 0.439s]
finished. total time: 1.044s
$
$ fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.445s]
finished. total time: 1.026s
$
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (258344 KB)...
OKAY [ 8.888s]
writing 'system'...
OKAY [ 5.917s]
finished. total time: 14.805s
$
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256570 KB)...
OKAY [ 9.039s]
writing 'system'...
OKAY [ 5.509s]
finished. total time: 14.548s
$
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (246510 KB)...
OKAY [ 9.312s]
writing 'system'...
OKAY [ 6.536s]
finished. total time: 15.847s
$
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 8.987s]
writing 'system'...
OKAY [ 7.513s]
finished. total time: 16.500s
$
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (261322 KB)...
OKAY [ 8.816s]
writing 'system'...
OKAY [ 11.196s]
finished. total time: 20.012s
$
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 9.297s]
writing 'system'...
OKAY [ 5.525s]
finished. total time: 14.823s
$
$ fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (262143 KB)...
OKAY [ 9.387s]
writing 'system'...
OKAY [ 6.682s]
finished. total time: 16.069s
$
$ fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (256817 KB)...
OKAY [ 9.803s]
writing 'system'...
OKAY [ 6.820s]
finished. total time: 16.622s
$
$ fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (237909 KB)...
OKAY [ 8.308s]
writing 'system'...
OKAY [ 7.428s]
finished. total time: 15.736s
$
$ fastboot flash system system.img_sparsechunk.9
error: cannot load 'system.img_sparsechunk.9': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.10error: cannot load 'system.img_sparsechunk.10': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.11error: cannot load 'system.img_sparsechunk.11': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.12error: cannot load 'system.img_sparsechunk.12': No such file or directory
$
$ fastboot flash system_b system_other.img
error: cannot load 'system_other.img': No such file or directory
$
$ fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [ 5.175s]
writing 'oem'...
OKAY [ 7.627s]
finished. total time: 12.803s
$
$ fastboot flash oem_b oem_other.img
error: cannot load 'oem_other.img': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.0
error: cannot load 'vendor.img_sparsechunk.0': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.1
error: cannot load 'vendor.img_sparsechunk.1': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.3
error: cannot load 'vendor.img_sparsechunk.3': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.4
error: cannot load 'vendor.img_sparsechunk.4': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.5
error: cannot load 'vendor.img_sparsechunk.5': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.6
error: cannot load 'vendor.img_sparsechunk.6': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.7
error: cannot load 'vendor.img_sparsechunk.7': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.8
error: cannot load 'vendor.img_sparsechunk.8': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.9
error: cannot load 'vendor.img_sparsechunk.9': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.10error: cannot load 'vendor.img_sparsechunk.10': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.11error: cannot load 'vendor.img_sparsechunk.11': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.12error: cannot load 'vendor.img_sparsechunk.12': No such file or directory
$
$ fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.078s]
finished. total time: 0.078s
$
$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.124s]
finished. total time: 0.124s
$
$ fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.002s]
finished. total time: 0.002s
$
$ fastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.003s
$
$ fastboot reboot
rebooting...
finished. total time: 0.152s
braganetx said:
Yes, locked bootloader
HTML:
$ fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
$
$ fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
$
$ fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.085s]
finished. total time: 0.104s
$
$ fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.192s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.553s]
finished. total time: 0.745s
$
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (66358 KB)...
OKAY [ 2.296s]
writing 'modem'...
OKAY [ 1.046s]
finished. total time: 3.343s
$
$ fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (2956 KB)...
OKAY [ 0.115s]
writing 'fsg'...
OKAY [ 0.103s]
finished. total time: 0.218s
$
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
$
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
$
$ fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin': No such file or directory
$
$ fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin': No such file or directory
$
$ fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 0.090s]
writing 'logo'...
OKAY [ 0.096s]
finished. total time: 0.187s
$
$ fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.605s]
writing 'boot'...
OKAY [ 0.439s]
finished. total time: 1.044s
$
$ fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.445s]
finished. total time: 1.026s
$
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (258344 KB)...
OKAY [ 8.888s]
writing 'system'...
OKAY [ 5.917s]
finished. total time: 14.805s
$
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256570 KB)...
OKAY [ 9.039s]
writing 'system'...
OKAY [ 5.509s]
finished. total time: 14.548s
$
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (246510 KB)...
OKAY [ 9.312s]
writing 'system'...
OKAY [ 6.536s]
finished. total time: 15.847s
$
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 8.987s]
writing 'system'...
OKAY [ 7.513s]
finished. total time: 16.500s
$
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (261322 KB)...
OKAY [ 8.816s]
writing 'system'...
OKAY [ 11.196s]
finished. total time: 20.012s
$
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 9.297s]
writing 'system'...
OKAY [ 5.525s]
finished. total time: 14.823s
$
$ fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (262143 KB)...
OKAY [ 9.387s]
writing 'system'...
OKAY [ 6.682s]
finished. total time: 16.069s
$
$ fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (256817 KB)...
OKAY [ 9.803s]
writing 'system'...
OKAY [ 6.820s]
finished. total time: 16.622s
$
$ fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (237909 KB)...
OKAY [ 8.308s]
writing 'system'...
OKAY [ 7.428s]
finished. total time: 15.736s
$
$ fastboot flash system system.img_sparsechunk.9
error: cannot load 'system.img_sparsechunk.9': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.10error: cannot load 'system.img_sparsechunk.10': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.11error: cannot load 'system.img_sparsechunk.11': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.12error: cannot load 'system.img_sparsechunk.12': No such file or directory
$
$ fastboot flash system_b system_other.img
error: cannot load 'system_other.img': No such file or directory
$
$ fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [ 5.175s]
writing 'oem'...
OKAY [ 7.627s]
finished. total time: 12.803s
$
$ fastboot flash oem_b oem_other.img
error: cannot load 'oem_other.img': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.0
error: cannot load 'vendor.img_sparsechunk.0': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.1
error: cannot load 'vendor.img_sparsechunk.1': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.3
error: cannot load 'vendor.img_sparsechunk.3': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.4
error: cannot load 'vendor.img_sparsechunk.4': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.5
error: cannot load 'vendor.img_sparsechunk.5': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.6
error: cannot load 'vendor.img_sparsechunk.6': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.7
error: cannot load 'vendor.img_sparsechunk.7': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.8
error: cannot load 'vendor.img_sparsechunk.8': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.9
error: cannot load 'vendor.img_sparsechunk.9': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.10error: cannot load 'vendor.img_sparsechunk.10': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.11error: cannot load 'vendor.img_sparsechunk.11': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.12error: cannot load 'vendor.img_sparsechunk.12': No such file or directory
$
$ fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.078s]
finished. total time: 0.078s
$
$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.124s]
finished. total time: 0.124s
$
$ fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.002s]
finished. total time: 0.002s
$
$ fastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.003s
$
$ fastboot reboot
rebooting...
finished. total time: 0.152s
Click to expand...
Click to collapse
I can see a few errors where have typos eg dsp in the commands and you are also trying to flash a lot of stuff that simply doesn't exist
You've also erased stuff that doesn't need erasing and hopefully won't cause an issue
Please use the following commands to flash your firmware and in the order shown below and I presume you are using the following firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
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
TheFixItMan said:
I can see a few errors where have typos eg dsp in the commands and you are also trying to flash a lot of stuff that simply doesn't exist
You've also erased stuff that doesn't need erasing and hopefully won't cause an issue
Please use the following commands to flash your firmware and in the order shown below and I presume you are using the following firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
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
Click to expand...
Click to collapse
I ran the commands as suggested, but even so it does not enter the system, I notice that it gives a slight wink on the screen but does not enter the system it enters the recovery menu.
Code:
$ fastboot oem fb_mode_set
...
OKAY [ 0.012s]
finished. total time: 0.012s
$ fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.034s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.099s]
finished. total time: 0.133s
$ fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.575s]
finished. total time: 0.790s
$ fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 0.104s]
writing 'logo'...
OKAY [ 0.119s]
finished. total time: 0.223s
$ fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.655s]
writing 'boot'...
OKAY [ 0.446s]
finished. total time: 1.102s
$ fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.454s]
finished. total time: 1.143s
$ fastboot flash dsp adspso.bin
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.597s]
writing 'dsp'...
OKAY [ 0.293s]
finished. total time: 0.890s
$ fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [ 5.711s]
writing 'oem'...
OKAY [ 7.667s]
finished. total time: 13.378s
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (258344 KB)...
OKAY [ 9.917s]
writing 'system'...
OKAY [ 5.930s]
finished. total time: 15.847s
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256570 KB)...
OKAY [ 9.641s]
writing 'system'...
OKAY [ 5.534s]
finished. total time: 15.175s
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (246510 KB)...
OKAY [ 10.827s]
writing 'system'...
OKAY [ 6.586s]
finished. total time: 17.413s
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 11.385s]
writing 'system'...
OKAY [ 7.547s]
finished. total time: 18.932s
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (261322 KB)...
OKAY [ 11.734s]
writing 'system'...
OKAY [ 11.231s]
finished. total time: 22.965s
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 11.661s]
writing 'system'...
OKAY [ 5.534s]
finished. total time: 17.196s
$ fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (262143 KB)...
OKAY [ 11.027s]
writing 'system'...
OKAY [ 6.719s]
finished. total time: 17.746s
$ fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (256817 KB)...
OKAY [ 10.969s]
writing 'system'...
OKAY [ 6.857s]
finished. total time: 17.826s
$ fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (237909 KB)...
OKAY [ 10.007s]
writing 'system'...
OKAY [ 7.431s]
finished. total time: 17.438s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (66358 KB)...
OKAY [ 2.825s]
writing 'modem'...
OKAY [ 1.060s]
finished. total time: 3.885s
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.064s]
finished. total time: 0.064s
$ fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (2956 KB)...
OKAY [ 0.153s]
writing 'fsg'...
OKAY [ 0.132s]
finished. total time: 0.285s
$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.024s
$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.171s]
finished. total time: 0.171s
$ fastboot oem fb_mode_clear
...
OKAY [ 0.014s]
finished. total time: 0.014s
$ fastboot reboot
rebooting...
finished. total time: 0.166s
$
braganetx said:
I ran the commands as suggested, but even so it does not enter the system, I notice that it gives a slight wink on the screen but does not enter the system it enters the recovery menu.
Code:
$ fastboot oem fb_mode_set
...
OKAY [ 0.012s]
finished. total time: 0.012s
$ fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.034s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.099s]
finished. total time: 0.133s
$ fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.575s]
finished. total time: 0.790s
$ fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 0.104s]
writing 'logo'...
OKAY [ 0.119s]
finished. total time: 0.223s
$ fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.655s]
writing 'boot'...
OKAY [ 0.446s]
finished. total time: 1.102s
$ fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.454s]
finished. total time: 1.143s
$ fastboot flash dsp adspso.bin
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.597s]
writing 'dsp'...
OKAY [ 0.293s]
finished. total time: 0.890s
$ fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [ 5.711s]
writing 'oem'...
OKAY [ 7.667s]
finished. total time: 13.378s
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (258344 KB)...
OKAY [ 9.917s]
writing 'system'...
OKAY [ 5.930s]
finished. total time: 15.847s
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256570 KB)...
OKAY [ 9.641s]
writing 'system'...
OKAY [ 5.534s]
finished. total time: 15.175s
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (246510 KB)...
OKAY [ 10.827s]
writing 'system'...
OKAY [ 6.586s]
finished. total time: 17.413s
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 11.385s]
writing 'system'...
OKAY [ 7.547s]
finished. total time: 18.932s
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (261322 KB)...
OKAY [ 11.734s]
writing 'system'...
OKAY [ 11.231s]
finished. total time: 22.965s
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 11.661s]
writing 'system'...
OKAY [ 5.534s]
finished. total time: 17.196s
$ fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (262143 KB)...
OKAY [ 11.027s]
writing 'system'...
OKAY [ 6.719s]
finished. total time: 17.746s
$ fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (256817 KB)...
OKAY [ 10.969s]
writing 'system'...
OKAY [ 6.857s]
finished. total time: 17.826s
$ fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (237909 KB)...
OKAY [ 10.007s]
writing 'system'...
OKAY [ 7.431s]
finished. total time: 17.438s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (66358 KB)...
OKAY [ 2.825s]
writing 'modem'...
OKAY [ 1.060s]
finished. total time: 3.885s
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.064s]
finished. total time: 0.064s
$ fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (2956 KB)...
OKAY [ 0.153s]
writing 'fsg'...
OKAY [ 0.132s]
finished. total time: 0.285s
$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.024s
$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.171s]
finished. total time: 0.171s
$ fastboot oem fb_mode_clear
...
OKAY [ 0.014s]
finished. total time: 0.014s
$ fastboot reboot
rebooting...
finished. total time: 0.166s
$
Click to expand...
Click to collapse
If you enter bootloader mode and then select start normally from the menu option does the phone boot normally? You can also try safe mode
As your bootloader is locked it will be very hard to fix if it doesn't start normally from this option
You may have a hardware fault if the bootloader has never been unlocked - obviously if you have relocked it after modding your phone this could cause issues which is why you should never re-lock the bootloader after unlocking it
TheFixItMan said:
If you enter bootloader mode and then select start normally from the menu option does the phone boot normally?
Click to expand...
Click to collapse
Yes, I tried, but I didn't start, as I mentioned just a slight wink.
You can also try safe mode
Click to expand...
Click to collapse
How can I start safe mode without accessing the system?
As your bootloader is locked it will be very hard to fix if it doesn't start normally from this option
You may have a hardware fault if the bootloader has never been unlocked - obviously if you have relocked it after modding your phone this could cause issues which is why you should never re-lock the bootloader after unlocking it
Click to expand...
Click to collapse
braganetx said:
How can I start safe mode without accessing the system?
Click to expand...
Click to collapse
Option in bootloader menu
As stated if it doesn't boot there's not anything else you can do as your bootloader is locked
If you have never unlocked it then it could be a hardware fault
You will need to take it to a repair shop for diagnosis
TheFixItMan said:
Option in bootloader menu
As stated if it doesn't boot there's not anything else you can do as your bootloader is locked
If you have never unlocked it then it could be a hardware fault
You will need to take it to a repair shop for diagnosis
Click to expand...
Click to collapse
OK.
I appreciate the help, it seems that it is a hardware problem, apparently, there is no logic to not work.
braganetx said:
OK.
I appreciate the help, it seems that it is a hardware problem, apparently, there is no logic to not work.
Click to expand...
Click to collapse
Try using mmcblk0 file method, Maybe it can able to boot the device.
riyan65 said:
Try using mmcblk0 file method, Maybe it can able to boot the device.
Click to expand...
Click to collapse
But this method is when it’s not even entering fastboot, so what did I see here in research or not?
Because mine enters fastboot normally even in the recovery menu just does not start the system
braganetx said:
But this method is when it’s not even entering fastboot, so what did I see here in research or not?
Because mine enters fastboot normally even in the recovery menu just does not start the system
Click to expand...
Click to collapse
The image contain all system files with bootloader and firmware, so I just suggest you to try that method. And your device also not working, you can try this method.

Moto z2 force Flash Stock Wifi Issues x1789-04 tmobile

Notice there is a huge issue with the modem in another post https://forum.xda-developers.com/z2-force/help/0-imei-pie-xt-1789-03-sprint-t3957851 please stay tune
I am having an issue with Wifi, I attempted to update lineage os 17.1 did process to clean flash. After did all the process provided with the guide of lineage os official wiki of my moto Z2 when it booted it got stuck on the loop lineage logo for over 15 minutes than usual with it configures. I decided to flash it back to stock, did a script for it of course(using an example of rcmaehl here XDA) due to long periods test fail I was able to boot it in stock oreo, but when I got to set it up, it does not show any wifi and not even data of carrier. went to the bootloader again to notice that broadband is unknown(not found). long story short I have a half soft brick phone. Any idea and suggestion.
The script I was able to make flash to stock oreo:
Code:
@echo off
adb reboot bootloader
fastboot --set-active=a
ECHO Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a 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_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to rebooting to flash to B.
pause
adb reboot bootloader
pause
adb --set-active=b
echo Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a 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_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to reboot.
pause
fastboot reboot
Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.
41rw4lk said:
Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.
Click to expand...
Click to collapse
I attempted as avised with script convertor of RootJunky. First attempt running the script
Code:
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.000s]
Finished. Total time: 0.000s
(bootloader) is-logical:partition: not found
Sending 'partition' (206 KB) OKAY [ 0.016s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.185s]
Finished. Total time: 0.216s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.331s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.169s]
Finished. Total time: 0.501s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (97431 KB) ^CTerminate batch job (Y/N)? n
Sending 'fsg' (5596 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.135s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.594s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (3151 KB) OKAY [ 0.085s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (23357 KB) OKAY [ 0.721s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516201 KB) OKAY [ 16.038s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (495129 KB) OKAY [ 15.564s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (519125 KB) OKAY [ 16.524s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523779 KB) OKAY [ 16.152s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516309 KB) OKAY [ 16.016s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (420583 KB) OKAY [ 13.061s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system_b: not found
Sending 'system_b' (515183 KB) OKAY [ 16.010s]
Writing 'system_b' OKAY [ 2.907s]
Finished. Total time: 25.177s
(bootloader) is-logical:system_b: not found
Sending 'system_b' (307220 KB) OKAY [ 9.615s]
Writing 'system_b' OKAY [ 1.648s]
Finished. Total time: 14.835s
(bootloader) is-logical:oem__a: not found
Sending 'oem__a' (175682 KB) OKAY [ 5.476s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'modemst2' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'carrier' OKAY [ 0.001s]
Finished. Total time: 0.004s
Erasing 'cache' OKAY [ 0.000s]
Finished. Total time: 0.004s
Erasing 'userdata' OKAY [ 0.075s]
Finished. Total time: 0.082s
Erasing 'ddr' OKAY [ 0.001s]
Finished. Total time: 0.006s
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5596 KB) OKAY [ 0.173s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.137s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.001s]
Finished. Total time: 0.004s
I notice the error, then proceeded to fix which it should be flash. all it flashes well, but went attempt to reboot to see if system boots up and go back to bootloader .
I'm aware that my scripting is the worst:laugh:, but funny part it got the job done to able to see the system up and running of course without data or wifi connection. :silly: I do appreciate the assistance and Hopefully keep having the assist with suggestions or guides of course. thankfully I have back up the phone(Not Moto z2) but really wish to go back this phone to able to use it as my main again...
If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.
it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?
insanegrim said:
it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?
Click to expand...
Click to collapse
Go back to fastboot and flash the modem only.
fastboot flash modem (drag and drop the NON-HLOS.bin from your firmware here)
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
If that doesn't work it may be possible that your persist partition is full and not letting the modem initialize. You'll need root for this.
adb shell
su
cd /mnt/vendor/persist/cache/recovery
rm log
rm last_log
exit
exit
adb reboot
41rw4lk said:
If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.
Click to expand...
Click to collapse
This soft bricked and now it bootloops my xt1789-04

MOTO G8 ENTERING THE FASTBOOT SCREEN AND DOES NOT START

Hello friends, how are you?
I'm Jeferson and I'm sorry if I'm in the wrong place and (my English).
I have a Moto G8 XT2045-1 it is going straight to the fastboot screen after an android error.
I tried to pass the software on it through "RESCUE" it completes successfully but the device appears the motorola logo and restarts (this process happens 4 times) after that it enters a FAIL BOOT screen.
I tried to use some ADB commands but I don't have much knowledge about these commands, I'll leave the commands I used and their results, in case anyone has gone through this problem I appreciate any help.
Thanks.
Cod.
fastboot oem fb_mode_set
fastboot getvar max-sparse-size
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 system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Result.
fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.004s
fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
fastboot flash partition gpt.bin
target reported max download size of 805263360 bytes
sending 'partition' (37 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.383s]
finished. total time: 0.389s
fastboot flash bootloader bootloader.img
target reported max download size of 805263360 bytes
sending 'bootloader' (14204 KB)...
OKAY [ 0.343s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'uefi_sec.mbn' to 'uefisecapp'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'qupfw.elf' to 'qupfw'
(bootloader) - flashing 'xbl_config.elf' to 'xbl_config'
(bootloader) - flashing 'xbl.elf' to 'xbl'
OKAY [ 0.349s]
finished. total time: 0.696s
fastboot flash logo logo.bin
target reported max download size of 805263360 bytes
sending 'logo' (2667 KB)...
OKAY [ 0.063s]
writing 'logo'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.203s
fastboot flash boot boot.img
target reported max download size of 805263360 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.499s]
writing 'boot'...
OKAY [ 0.915s]
finished. total time: 2.421s
fastboot flash recovery recovery.img
target reported max download size of 805263360 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.472s]
writing 'recovery'...
OKAY [ 1.087s]
finished. total time: 2.562s
fastboot flash dsp adspso.bin
error: cannot load 'adspso.bin'
fastboot flash oem oem.img
error: cannot load 'oem.img'
fastboot flash system system.img_sparsechunk.0
error: cannot load 'system.img_sparsechunk.0'
fastboot flash system system.img_sparsechunk.1
error: cannot load 'system.img_sparsechunk.1'
fastboot flash system system.img_sparsechunk.2
error: cannot load 'system.img_sparsechunk.2'
fastboot flash system system.img_sparsechunk.3
error: cannot load 'system.img_sparsechunk.3'
fastboot flash system system.img_sparsechunk.4
error: cannot load 'system.img_sparsechunk.4'
fastboot flash system system.img_sparsechunk.5
error: cannot load 'system.img_sparsechunk.5'
fastboot flash system system.img_sparsechunk.6
error: cannot load 'system.img_sparsechunk.6'
fastboot flash system system.img_sparsechunk.7
error: cannot load 'system.img_sparsechunk.7'
fastboot flash system system.img_sparsechunk.8
error: cannot load 'system.img_sparsechunk.8'
fastboot flash system system.img_sparsechunk.9
error: cannot load 'system.img_sparsechunk.9'
fastboot flash system system.img_sparsechunk.10
error: cannot load 'system.img_sparsechunk.10'
fastboot flash system system.img_sparsechunk.11
error: cannot load 'system.img_sparsechunk.11'
fastboot flash system system.img_sparsechunk.12
error: cannot load 'system.img_sparsechunk.12'
fastboot flash system system.img_sparsechunk.13
error: cannot load 'system.img_sparsechunk.13'
fastboot flash system system.img_sparsechunk.14
error: cannot load 'system.img_sparsechunk.14'
fastboot flash modem NON-HLOS.bin
error: cannot load 'NON-HLOS.bin'
fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.014s]
finished. total time: 0.015s
fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.005s]
finished. total time: 0.008s
fastboot flash fsg fsg.mbn
error: cannot load 'fsg.mbn'
fastboot erase cache
erasing 'cache'...
OKAY [ 0.002s]
finished. total time: 0.004s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.219s]
finished. total time: 0.220s
fastboot reboot

Categories

Resources