Database Info

Motorola Moto G3 XT1541

Hi,
I've got a Motorola Moto G XT1541.
Being an android newbie, and bored one time I tried to root my device with what I think was the KingRoot App, and being stupid and not bothering to read to much up about it (as I wanted to store apps on the SD card as internal memory is limited) it obviously bricked my phone! It currently only boots up in the fastboot mode only stating:
"Start up failed. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
AP Fastboot Flash mode(secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image"
Details on the device: Device is locked. status code: 0. Osprey XT1541. (Any other specifics needed just ask).
I have attempted to flash the firmware back to standard again which hasn't worked. (Obviously I'm doing something wrong!) the answers to the commands i have included below.
fastboot flash partition gpt.bin
sending partition okay
wiriting partition... INFOPreflash validation failed FAILED (remote failure)
fastboot flash motoboot boot.img
sending motoboot okay
writing 'flash'... INFOPermission denied FAILED (Remote failure)
fastboot flash logo logo.bin
sending logo.. okay
writing logo.. okay
fastboot flash boot boot.img
sending boot ... okay
writing boot... INFOPREFlash validation failed
fastboot flash recovery recovery.img
sending recovery .. okay
writing recover.. okay
fastboot flash system system.img_sparsechunk1
error: cannot load 'system.img_sparsechunk1'
fastboot flash system system.img_sparsechunk2
error: cannot load 'system.img_sparsechunk2'
fastboot flash system system.img_sparsechunk3
error: cannot load 'system.img_sparsechunk3'
fastboot flash modem NON-HLOS.bin
sending modem... okay
writing modem... okay
fastboot erase modemst1
erasing modemst1... okay
fastboot erase modemst2
erasing modemst2... okay
fastboot flash fsg fsg.mbn
sending fsg... okay
writing fsg... okay
fastboot erase cache
erasing cache... okay
fastboot erase userdata
erasing userdata... okay
fastboot reboot
Any help would be greatly appreciated as trying to learn this as I go
Thanks

Anyone with any ideas?

Which firmare are you trying to install? The newest one? It also seems you didn't unpack images correctly.

Acetyloaceton said:
Which firmare are you trying to install? The newest one? It also seems you didn't unpack images correctly.
Click to expand...
Click to collapse
I'm trying to install the factory firmware for the phone so it's MotoG3 Osprey XT1541 Retail GB downloaded from somewhere on this site if i remember correctly.
What do you mean by unpack the images? I extracted the firmware out of the zip file and then copied it over into the fastboot folder.
Thanks for the reply

Looks like either thexml.zip archive or download was bad. Or else it wasn't unpacked correctly. Try downloading again and make sure that it's correct firmware. [emoji39] .
Edit: Also check for additional sparsechunk files in the extracted folder, you must flash all of them.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Looks like either thexml.zip archive or download was bad. Or else it wasn't unpacked correctly. Try downloading again and make sure that it's correct firmware. [emoji39] .
Edit: Also check for additional sparsechunk files in the extracted folder, you must flash all of them.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Okay will download the firmware again and see if it works

Which version of android did you have before stuck? Lollipop or marshmallow? These commands look like you are trying to flash lollipop. You can't do downgrades without unlocking bootloader. If I were you I would try to flash 6.0.1
1. Download firmware 1gb or 2gb (I dont know which version do you have).
2. Unpack it to folder with adb driver
3. Reboot to bootloader
4. Flash images:
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Remember to check how many sparsechunk do you have. If I remember correctly 6.0.1 have 0-7 sparsechunks

I think it was marshmellow, but not 100%! So i re-downloaded the firmware and redid all the steps however when going through the opening steps my phone cannot pick up a wifi network, so i'm assuming I've installed the wrong firmware onto the device now?
What information would i need to provide for you to confirm I've installed the correct firmware? I went for these drivers
https://www.androidfilehost.com/?w=...a551901007e63955ed25336c82cebd8339ed5c13843cc
Thanks for the help guys really appreciate it!

Acetyloaceton said:
Which version of android did you have before stuck? Lollipop or marshmallow? These commands look like you are trying to flash lollipop. You can't do downgrades without unlocking bootloader. If I were you I would try to flash 6.0.1
1. Download firmware 1gb or 2gb (I dont know which version do you have).
2. Unpack it to folder with adb driver
3. Reboot to bootloader
4. Flash images:
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Remember to check how many sparsechunk do you have. If I remember correctly 6.0.1 have 0-7 sparsechunks
Click to expand...
Click to collapse
As my phone isn't finding wifi would you recommend i redo the steps with the above firmware? instead of the firmware I've currently used? I'm guessing I can tell how many sparsechunks by checking the downloaded folder?

I remember someone had also this issue when he didnt do hard reset before flashing firmware. Go to recovery and do full factory reset. Here is guide. After it flash firmware again

Acetyloaceton said:
I remember someone had also this issue when he didnt do hard reset before flashing firmware. Go to recovery and do full factory reset. Here is guide. After it flash firmware again
Click to expand...
Click to collapse
This Worked! Thanks alot :good:

Unlocked bootloader in January Security Patch and Flashed LineageOS,now can't go back

Hello!
I was trying some custom ROMs on my XT 1550 and then went back to stock using the July security patch full firmware zip posted on XDA by @lost101.
->I updated to January security patch through system updates. I unlocked bootloader again and flashed LineageOS.
->Now when I type the commands used to flash the stock firmware,it shows "Preflash validation error". A quick search on XDA shows not to flash partition gpt .bin and bootloader,but even after skipping that,even the sparsechunk files are showing error-not signed,but I have earlier used them several times to go back to stock. My system was updated to January patch but I'm trying to flash july patch,as January patch for XT 1550 is not available in XDA for download.
Bootloader status: 3(unlocked)
I can boot to twrp,3.0.2-r5,but:
->data and cache can't be mounted
->custom ROMs can't be flashed again as a result of the above
I didn't have backups and I wiped the userdata while following the commands to relock bootloader.
For your kind reference,I generally went back to stock using these commands,specific to XT 1550:
fastboot devices
fastboot oem lock begin
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
Kindly help as it is my primary device and I can't boot it up into anything.

adb screen shows this:
C:\adb>fastboot devices
************** fastboot
C:\adb>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.038s]
finished. total time: 0.039s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.050s]
writing 'logo'...
OKAY [ 0.290s]
finished. total time: 0.344s
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.056s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.524s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.064s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (247489 KB)...
OKAY [ 7.764s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.218s
C:\adb>

Try with these commands
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Skip gpt.bin and bootloadet.img

Thanks a lot bro! You saved my device! Now if I want to relock bootloader for security,can I write "fastboot oem lock" on adb?

debopriyobasu said:
Thanks a lot bro! You saved my device! Now if I want to relock bootloader for security,can I write "fastboot oem lock" on adb?
Click to expand...
Click to collapse
No, you cannot relock the bootloader... The only way to relock is to flash a full signed image, and you did not... And you cannot flash a full signed image until the January security update image (or later version) is released.
There is no advantage to relocking the bootloader, your warranty is gone and it cannot be restored, and you will never lose the unlocked bootloader warning screen unless you flash a custom boot logo file, regardless if relock or not.

Thanks for the info! One last question: Can I update my system to January patch now? I'm getting system update notifications. I'm asking to be double sure such that I don't brick my device while updating with an unlocked bootloader. Thanks!

debopriyobasu said:
Thanks for the info! One last question: Can I update my system to January patch now? I'm getting system update notifications. I'm asking to be double sure such that I don't brick my device while updating with an unlocked bootloader. Thanks!
Click to expand...
Click to collapse
You can update with unlock bootloader but make sure to have stock recovery and unmodified files aka no root.
Regards
Ayan

Flashing Problems! :/
You need to wait to the next security patch... then flash all commands except fastboot oem lock begin and fastboot oem lock...... it works! the same thing happen with my old MotoX and i waited months! then i flashed and everything was fine!
I recommend you for your next ROM flashing experiments and updates to flash like this the patches...
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
you may try this commands! hope it works!:good:

Moto G7 Power Failing to restore restore orgional firmware

Hello all,
I have been trying to restore my Moto G7 Power to it's original firmware. I keep getting flash modem "NON-HOLS.bin fail.
I have followed so many methods and different tools and all failing.
I'm also getting permission denied when using adb fastboot.
I really need help on this, I'm definitely a noob here and need some guidance from the experts on this platform.
Thank you all in advance.

Solo-Play said:
Hello all,
I have been trying to restore my Moto G7 Power to it's original firmware. I keep getting flash modem "NON-HOLS.bin fail.
I have followed so many methods and different tools and all failing.
I'm also getting permission denied when using adb fastboot.
I really need help on this, I'm definitely a noob here and need some guidance from the experts on this platform.
Thank you all in advance.
Click to expand...
Click to collapse
Firmware you are trying to flash?
Model number?
Bootloader unlocked?
Sent from my mata using XDA Labs

Hello,
Phone is Moto G7 Power, Retail, XT1955-5, Ocean Retail
Bootloader was unlocked, then some how during my restore attempt it got locked. Unless I read it incorrectly. Not sure if there a way to confirm its locked.
Firmware. PPOS29.114-134-7-1
Hope this helps. Many thanks in advance

Solo-Play said:
Hello,
Phone is Moto G7 Power, Retail, XT1955-5, Ocean Retail
Bootloader was unlocked, then some how during my restore attempt it got locked. Unless I read it incorrectly. Not sure if there a way to confirm its locked.
Firmware. PPOS29.114-134-7-1
Hope this helps. Many thanks in advance
Click to expand...
Click to collapse
The bootloader says
Device: locked
Or
Device: unlocked
Sent from my mata using XDA Labs

sd_shadow said:
The bootloader says
Device: locked
Or
Device: unlocked[/QUOTE
At this point I'm not sure. Is there any easier way to find out?
Click to expand...
Click to collapse

Solo-Play said:
At this point I'm not sure. Is there any easier way to find out?
Click to expand...
Click to collapse
Yes see bootloader screen
Sent from my mata using XDA Labs

Download the LMSA tool and proper drivers. Do the recovery to flash the latest software, you should be good to go. Here is the link: https://www.motorola.com/us/lenovo-motorola-smart-assistant

WaterMan! said:
Download the LMSA tool and proper drivers. Do the recovery to flash the latest software, you should be good to go. Here is the link: https://www.motorola.com/us/lenovo-motorola-smart-assistant
Click to expand...
Click to collapse
Hello WaterMan. I have already tried it. It keeps on failing between 55 and 70%. I do get some other error messages such as partition delay.

Solo-Play said:
Hello WaterMan. I have already tried it. It keeps on failing between 55 and 70%. I do get some other error messages such as partition delay.
Click to expand...
Click to collapse
These are the commands you are using?
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
Are you sure you have the correct software channel firmware?
Try
Code:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
Then try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you don't get any errors try
Code:
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-bootloader
If that works
Try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
Post any errors
Sent from my mata using XDA Labs

sd_shadow said:
These are the commands you are using?
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
Are you sure you have the correct software channel firmware?
Try
Code:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
Then try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you don't get any errors try
Code:
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-bootloader
If that works
Try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
Post any errors
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Code:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
Then try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
the above codes worked.
However these codes didn't work at
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-bootloader
I got an error that says
example: (bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.518s
The answer about the right channel firmware. I think I have the right firmware. The one I downloaded was PPOS29.114-134-7-1 , this firmware same as the build number number on my phone in the setting menu

Solo-Play said:
the above codes worked.
However these codes didn't work at
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-bootloader
I got an error that says
example: (bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.518s
The answer about the right channel firmware. I think I have the right firmware. The one I downloaded was PPOS29.114-134-7-1 , this firmware same as the build number number on my phone in the setting menu
Click to expand...
Click to collapse
There are ~20 different software channels for Ocean
https://mirrors.lolinet.com/firmware/moto/ocean/official/
PPOS29.114-134-7-1 is just the build version not software channel
Like retail, retus, reteu...
It has radio files and apns for your carrier among other things
Sent from my mata using XDA Labs
---------- Post added at 05:08 PM ---------- Previous post was at 04:35 PM ----------
Software channel info is in
Settings/about phone
Sent from my mata using XDA Labs

Hello,
Thanks for replying. I've seen this website site before. And yes my phone is Retail, I bought it at Best Buy. I'm some what aware of different firmwares. My question is and forgive me for sounding dumb with a question. How can I tell or find out which firmware to get. Is there an easier way to find out or is there a program that could automatically download and fix the phone, I mean restore it to it's original state.
Once again, I greatly appreciate all the help, feedback and guidance

Solo-Play said:
Hello,
Thanks for replying. I've seen this website site before. And yes my phone is Retail, I bought it at Best Buy. I'm some what aware of different firmwares. My question is and forgive me for sounding dumb with a question. How can I tell or find out which firmware to get. Is there an easier way to find out or is there a program that could automatically download and fix the phone, I mean restore it to it's original state.
Once again, I greatly appreciate all the help, feedback and guidance
Click to expand...
Click to collapse
If you bought at Best Buy, I would think it was
Retus not Retail
Sent from my ocean using XDA Labs

sd_shadow said:
If you bought at Best Buy, I would think it was
Retus not Retail
Click to expand...
Click to collapse
I may have downloaded it in the past and ran it using RSD Lite and got the same error non-holos.bin
By the way, I used the LMSA tool provided by Motorola. It found the firmware and when I ran it , it gave me a delay error and fastboot fail
I wonder if there is a way or tool to force the firmware update and install on the phone.
Oh by the way when I turn on my phone I get an error message that reads ( Your device has loaded a different operating system. ) then boots up fine after pressing power button.
I honestly wish if there was a way to wipe everything clean on the phone and restore everything back just like the computer when installing Windows

Motorola Z3 play baseband brick HELPME PLEASE (u__u)

hello guys I'm new to this community !! I needed your help to restore my phone's baseband !! in fastboot mode baseband shows how not found !!! I already have the bootloader unlocked .. I would like using TWRP to flash baseband again ???
MY phone specs
BL:MBM3.0-becham_retail-8ca64c4-190220
Baseband: <not found>
Product/Variant: beckham XT1929-5 64GB PVT
if someone can help me with some method to solve with linux or zip flash i am very grateful thanks to all

I finally figured out how to recover a base band from motorola Z3 play !!!
NOTE: <<<< NEED BOOTLOADER UNLOCKED >>>>
After unlocking the bootloader I used this rom
<<<< XT1929-5_BECKHAM_RETBR_9.0_PPWS29.131-27-1-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC >>>
!!! To install the system on the smartphone
correcting the connection problem and corrupted IMEI
Comand line to INSTALL ROM IN ADB TOOLS:
----------------------------------------------------------------------------------------------------------
fastboot oem fb_mode_set
fastboot flash gpt_a gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.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_b system_other.img
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 carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
----------------------------------------------------------------------------
After installation the problem will be fixed I hope I helped it took me 3 days to solve this problem even having intermediate knowledge of android system !!!
for people who have no knowledge !! a wrong root can cause a briking baseband easily
my email for some help if you want !!
[email protected]

Relock bootloader

Part, anyone knows an effective method to lock the bootloader so that I have oem_locked written instead of flashing_locked? You unlocked with a code from the Motorola website, which is the official method. I did not modify anything and blocked it with fastboot oem_lock. From now on, instead of oem_locked, I have flashing_locked written. Re-unlocking with the fastboot oem_unlock command is possible without the use of a code from Motorola. Is it normal? Another interesting and strange thing is that after entering recovery mode and trying to install the update from the sd card, he gets the error that he cannot see the card. If he wants to upload updates via ADB he also gets an error. LMSA rescue flashing also crashes when switching to fastboot mode. In general, in fastboot mode, I should be able to flash the stock without unlocking the bootloader and no, I can do it because I also have an error
C: \ adb> fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical: modem_a: not found
Sending 'modem_a' (81048 KB) OKAY [2.072s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Yesterday I started the phone in edl mode and used blankflash. Then I wanted to flash the stock but had to unlock the bootloader. Or rather, there shouldn't be such a need. I do not know how to bring it to the factory state.

gorbatschoff said:
Part, anyone knows an effective method to lock the bootloader so that I have oem_locked written instead of flashing_locked? You unlocked with a code from the Motorola website, which is the official method. I did not modify anything and blocked it with fastboot oem_lock. From now on, instead of oem_locked, I have flashing_locked written. Re-unlocking with the fastboot oem_unlock command is possible without the use of a code from Motorola. Is it normal? Another interesting and strange thing is that after entering recovery mode and trying to install the update from the sd card, he gets the error that he cannot see the card. If he wants to upload updates via ADB he also gets an error. LMSA rescue flashing also crashes when switching to fastboot mode. In general, in fastboot mode, I should be able to flash the stock without unlocking the bootloader and no, I can do it because I also have an error
C: \ adb> fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical: modem_a: not found
Sending 'modem_a' (81048 KB) OKAY [2.072s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Yesterday I started the phone in edl mode and used blankflash. Then I wanted to flash the stock but had to unlock the bootloader. Or rather, there shouldn't be such a need. I do not know how to bring it to the factory state.
Click to expand...
Click to collapse
All of that happened to me except for the flashing locked and unlocked part, when I first got my phone before it was ever unlocked, it said flash_locked and I unlocked it and then it's flashing_unlocked. Now when I relock it, it goes back to it's original state, as flashing_locked. I get Motorola updates still so that's a plus to me.
Never had to start the phone in edl and hope I never have to.
Never used LMSA, and hope I never have to.
And my suggestion would be unlock the bootloader and flash stock firmware from lolinet and use these commands
↓
fastboot devices
fastboot set_active a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b 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_b system_b.img_sparsechunk.0 fastboot flash system_b system_b.img_sparsechunk.1 fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
↑
After that, boot it up for the first time and setup the phone. After seeing the home screen power off and boot to fastboot and lock your bootloader, the reason I say lock it is because there is no better reason to have it unlocked imo ("totally unnecessary, you can do what you want, I'm just trying to help ") because there isn't really a striving development community with ROMs yet. I think here soon there will be once Android 10 releases for this phone .

Thanks for the answer. I've used these commands and of course they work. The phone works but the ADB and recovery problem is still there. And that worries me.

dont work
SnowTalker said:
All of that happened to me except for the flashing locked and unlocked part, when I first got my phone before it was ever unlocked, it said flash_locked and I unlocked it and then it's flashing_unlocked. Now when I relock it, it goes back to it's original state, as flashing_locked. I get Motorola updates still so that's a plus to me.
Never had to start the phone in edl and hope I never have to.
Never used LMSA, and hope I never have to.
And my suggestion would be unlock the bootloader and flash stock firmware from lolinet and use these commands
↓
fastboot devices
fastboot set_active a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b 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_b system_b.img_sparsechunk.0 fastboot flash system_b system_b.img_sparsechunk.1 fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
↑
After that, boot it up for the first time and setup the phone. After seeing the home screen power off and boot to fastboot and lock your bootloader, the reason I say lock it is because there is no better reason to have it unlocked imo ("totally unnecessary, you can do what you want, I'm just trying to help ") because there isn't really a striving development community with ROMs yet. I think here soon there will be once Android 10 releases for this phone .
Click to expand...
Click to collapse
dont work

bugy65 said:
dont work
Click to expand...
Click to collapse
The commands?