Database Info

How to flash Stock Kit Kat / no flashall.bat???

Hmm......maybe to easy but i was wondering how to flash Blur_Version.175.44.1.falcon_umts.Retail.en.DE (444MB Stock Kit Kat) which is which is available on sbf.droid-developers.org since a few days.
There is no flashall.bat in the zip.
I can not try myself. Forgot my phone at a friends place :crying:
Will have to wait for weekend to get it back or maybe by Mail.
Just by using Custom Recovery?
Maybe i should just ask my friend to do it, cause i wanna know :laugh:
Cannot wait flashing only one file instead of three when going back to stock.

Won't it void your warranty!? :S

It would void my guarantee but not my warranty.
I bought it in Germany. That's a EU directive.
And secondary i waited one month to see if everything works right.
Now i hope that no serious problems will come up.
And i want to flash a Stock Rom. So actually there is no need to Root or something cause it should be signed.

Found it here:
akaygee said:
relock bootloader
=============
download adb and fastboot extract or place into a directory.
now download the factory firmware image of your phone extract zip/rar and place into the same directory.
download "relock bootloader.txt" rename to "relock bootloader.bat" place this in the same directory as the files and double click it ,this would save you typing in all the commands from below in by hand and does it all for you.recap....if you did download and run relock bootloader.bat you dont need to type anything form below
open a command prompt as administrator ,navigate to the directory where you placed all the files we are working with and type as follows giving time for each command to finish.
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Click to expand...
Click to collapse
Sure the relock Stuff can be ignored.
And for the sparsechunk remember:
spiritflare said:
Just remember that unless you download the Motorola version of FASTBOOT, you won't be able to flash the Sparsechunk files...
You will get:
C:\sdk-tools>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
Once I downloaded the Motorola version of fastboot from here: http://theunlockr.com/2013/12/06/unroot-motorola-moto-g/ (see link in this article) - - - (or just google for Motorola g fastboot)
Also, the final step here, it says:
C:\sdk-tools>fastboot oem lock
... FAILED (status read failed (Too many links))
finished. total time: 17.659s
it will still lock the bootloader - you can verify by reboot the device and you will see bootloader status "Locked"
Hope this helps
Click to expand...
Click to collapse

[HELP] Locked the bootloader, warning logo still there

Hi guys,
I just went back to stock android since my Moto G allegedly received the Official Lolipop update. But the bootloader remains unlocked
Device:XT1033
Here are the commands i did
Code:
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
Result of the first command:
Code:
mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 2.652s]
finished. total time: 2.652s
Result of the last command:
Code:
mfastboot.exe oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 17.924s
When I tried to check whether if it was locked for real or not I rebooted to bootloader and it says
Device is locked: Status Code:2
Click to expand...
Click to collapse
But i still get the dreaded
WARNING BOOTLOADER UNLOCKED
Click to expand...
Click to collapse
screen at the beginning. So, i tried flashing the logo.bin again but all my attempts are in vain.

Yeah that's because once it's unlocked you can't lock it again. There are three statuses 0-locked 3-unlocked 2-RELOCKED. So you can't actually 'lock' the boot loader once it's unlocked.

Failed to erase partition...getting desperate here

Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.

Try using mfastboot:
https://www.androidfilehost.com/?fid=23578570567719065​
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata​
Is the phone definitely an XT1033 Dual-SIM?

lost101 said:
Try using mfastboot:
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata​
Is the phone definitely an XT1033 Dual-SIM?
Click to expand...
Click to collapse
Yes sir it was bought in Saudi (asia) and is dual sim. The box also states that it is xt1033.
I have tried what you have suggested but the error still remains.
C:\Users\...\Desktop\mfastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 14.955s
C:\Users\...\Desktop\mfastboot>mfastboot erase userdata[/U]
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.953s
If it is of any help, the screen says that it has 41.18 bootloader, I don't exactly know what this information is for.

Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​

lost101 said:
Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
Click to expand...
Click to collapse
I already tried sir along with the Brazilian firmware and both returned the same error. The same partition error,
I get stuck right at the first command "mfastboot flash partition gpt.bin", it says the the phone couldn't erase the partition. I'm starting to hate motorola right now
The money I saved just to buy this phone and I only got to use it for 1 month.
I understand that my partition is likely messed up or is corrupted even though I did nothing with my phone except upgrading it to lollilop (biggest mistake ever), what I don't understand is there aren't anyone else here in the forum who seem to have the same problem as mine, its like I am the only who has this kind of error so there are no threads at all discussing on how to solve this.

You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img​
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

lost101 said:
You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img​
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8480 KB)...
OKAY [ 5.306s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.424s

titan015 said:
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
Click to expand...
Click to collapse
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​

lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​
Click to expand...
Click to collapse
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"

Try another recovery.img just in case that one was a bad download.

titan015 said:
Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.
Click to expand...
Click to collapse
I have the same problem, do you managed to fix it?

kesy85 said:
I have the same problem, do you managed to fix it?
Click to expand...
Click to collapse
no. i've tried just about everything, didn't managed to fix it

hi
i have the same problem too bro, im from the philippines too..
have u fixed it yet?

no fix?
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.

Same for me, BUMP
hand_solo said:
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.
Click to expand...
Click to collapse
Anyone managed to fix this?

The best I've found...
hand_solo said:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
Click to expand...
Click to collapse
...is this:
Cant flash GPT / Motoboot:
Use another firmware, try for another android versions.
Fastboot Error: preflash validation failed
Try your original (or last flashed) firmware.
Click to expand...
Click to collapse
from this thread: http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076/
P.s.: I have the same problem.

titan015 said:
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"
Click to expand...
Click to collapse
lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​
Click to expand...
Click to collapse
For me the error is:
Code:
fastboot flash recovery twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
target reported max download size of 536870912 bytes
[COLOR="SeaGreen"]sending 'recovery' (9372 KB)...
OKAY [ 0.377s]
[/COLOR]writing 'recovery'...
[COLOR="Red"][B](bootloader) Permission denied
FAILED (remote failure)[/B][/COLOR]
finished. total time: 0.408s
Same thing when I try to boot instead of Flashing
Code:
fastboot boot twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
[COLOR="SeaGreen"]downloading 'boot.img'...
OKAY [ 0.347s][/COLOR]
booting...
[B][COLOR="Red"]FAILED (remote failure)
[/COLOR][/B]finished. total time: 0.354s

An unlocked Bootloader is required to flash (or boot) a custom recovery.

lost101 said:
An unlocked Bootloader is required to flash (or boot) a custom recovery.
Click to expand...
Click to collapse
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.

Der_K said:
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.
Click to expand...
Click to collapse
Please try to explain more clearly. Don't use the term ROM, if you are talking about a factory firmware image - in other words - sparsechunk files.
Can you flash the stock recovery img included in the factory firmware image?

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:

Firmware oficial 9.0.0 Pie (Instalacion)

Hello everyone, I present you how to install Android Pie 9.0.0 stock on your device Moto Z3 Play, remember to follow the indications any doubt write it in the comments please.:
Requirements:
- You can do both with the bootloader blocked and unlocked
- Have ADB and Fastboot installed: https://forum.xda-developers.com/showthread.php?t=2317790
- Have Motorola drivers installed
- Download official Pie 9.0.0 firmware: https://forum.xda-developers.com/z3-play/how-to/android-9-0-pie-rolling-brazil-t3900061/page5 Pag. 5 Post #45
BECKHAM_PPW29.131_27_1_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml
credits to the user @tb110188 for uploading Onedrive
Process:
- Place the device in Bootloader mode connecting the device to the PC waiting for a few seconds to recognize it. After downloading the firmware we will have a folder where in the command console enter:
adb devices
Then adb reboot bootloader which will put the device in bootloader mode
- Enter the command:
fastboot devices to verify that it is recognized by the PC.
then the following:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash 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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot reboot
When entering this last command the device will reboot and show us the initial screen of Android Pie 9.0.0
Notes:
- These commands can be omitted to avoid having problems with the telephone signal (it is unlikely to happen but it is good to prevent)
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
- - This command will erase what is stored in the internal memory of the device, if you want to keep your data omit it
fastboot erase userdata

There's na even easier way to do that, using the Lenovo Moto Smart Assistant to Update the device...

Please elaborate!
I am about to receive my Z3Play and I cannot remember how I upgraded my Z2Play to Oreo but I recall I was using some Motorola software.
Sent from my Moto Z2 Play using Tapatalk

Model
Vegeta. said:
Hello everyone, I present you how to install Android Pie 9.0.0 stock on your device Moto Z3 Play, remember to follow the indications any doubt write it in the comments please.:
Requirements:
- Bootloader unlocked
- Have ADB and Fastboot installed: https://forum.xda-developers.com/showthread.php?t=2317790
- Have Motorola drivers installed
- Download official Pie 9.0.0 firmware: https://forum.xda-developers.com/z3-play/how-to/android-9-0-pie-rolling-brazil-t3900061/page5 Pag. 5 Post #45
BECKHAM_PPW29.131_27_1_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml
credits to the user @tb110188 for uploading Onedrive
Process:
- Place the device in Bootloader mode connecting the device to the PC waiting for a few seconds to recognize it. After downloading the firmware we will have a folder where in the command console enter:
adb devices
Then adb reboot bootloader which will put the device in bootloader mode
- Enter the command:
fastboot devices to verify that it is recognized by the PC.
then the following:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash 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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot reboot
When entering this last command the device will reboot and show us the initial screen of Android Pie 9.0.0
Notes:
- These commands can be omitted to avoid having problems with the telephone signal (it is unlikely to happen but it is good to prevent)
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
- - This command will erase what is stored in the internal memory of the device, if you want to keep your data omit it
fastboot erase userdata
Click to expand...
Click to collapse
Can it be installed in XT1929-6 with motorola assistant? I'm from Mexico and the OTA don't arrive

dreamerbl said:
Can it be installed in XT1929-6 with motorola assistant? I'm from Mexico and the OTA don't arrive
Click to expand...
Click to collapse
Yes, I installed today and everything works fine. Just follow the instructions.
Si, lo instalé hoy y todo funciona bien, solo sigue las instrucciones. En mi caso no tuve que desbloquear el bootloader.

Worked perfectly on 2 XT1929-8. Thanks!

SonoranEZR said:
Yes, I installed today and everything works fine. Just follow the instructions.
Si, lo instalé hoy y todo funciona bien, solo sigue las instrucciones. En mi caso no tuve que desbloquear el bootloader.
Click to expand...
Click to collapse
¿You're from México? I could use a little help bro. Thank you anyway :fingers-crossed:

dreamerbl said:
¿You're from México? I could use a little help bro. Thank you anyway :fingers-crossed:
Click to expand...
Click to collapse
Yes. I am from Mexico.
As for the instructions, follow them how they are, I omitted these commands:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
(Apparently this is to avoid signal loss according to the post, just in case .)
fastboot erase userdata
(This avoids having to reconfigure your Moto Z3 Play.)
This command gave me an error:
fastboot erase DDR
(invalid partition name DDR) but didn't cause problems with the installation or the use of my phone, I do not know if it is specific to my Moto Z3 Play.
Once the firmware files were extracted, I put these commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot bluetooth flash BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase DDR
fastboot reboot
and that's it!.

I cant install it in mexico z3 play
SonoranEZR said:
Yes. I am from Mexico.
As for the instructions, follow them how they are, I omitted these commands:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
(Apparently this is to avoid signal loss according to the post, just in case .)
fastboot erase userdata
(This avoids having to reconfigure your Moto Z3 Play.)
This command gave me an error:
fastboot erase DDR
(invalid partition name DDR) but didn't cause problems with the installation or the use of my phone, I do not know if it is specific to my Moto Z3 Play.
Once the firmware files were extracted, I put these commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot bluetooth flash BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase DDR
fastboot reboot
and that's it!.
Click to expand...
Click to collapse
i've made the same commands as you but i got some errors
D:\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>fastboot flash bluetooth BTFM.bin
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.100s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
D:\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>fastboot flash dsp dspso.bin
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.380s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command fail
any help?
estoy atorado con unos comandos, me dio estos errores (arriba mencionados), ayudaaa porfa

tacochan said:
i've made the same commands as you but i got some errors
D:\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>fastboot flash bluetooth BTFM.bin
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.100s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
D:\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>fastboot flash dsp dspso.bin
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.380s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command fail
any help?
estoy atorado con unos comandos, me dio estos errores (arriba mencionados), ayudaaa porfa
Click to expand...
Click to collapse
Que firmware descargaste? El OPWS28.70_47_8?

tacochan said:
i've made the same commands as you but i got some errors
D:\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>fastboot flash bluetooth BTFM.bin
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.100s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
D:\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>fastboot flash dsp dspso.bin
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.380s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command fail
any help?
estoy atorado con unos comandos, me dio estos errores (arriba mencionados), ayudaaa porfa
Click to expand...
Click to collapse
Why you flashed, or tried to, the Oreo one??? Also is not safe trying to flash a ROM from another revice, even if it's basically the same sans few OEM modifications...
---------- Post added at 08:34 PM ---------- Previous post was at 08:32 PM ----------
SonoranEZR said:
Que firmware descargaste? El OPWS28.70_47_8?
Click to expand...
Click to collapse
Assuming you have the XP1929-5 RETBE, the pie firmware would be BECKHAM_PPW29.131_27_1_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml...

tb110188 said:
Why you flashed, or tried to, the Oreo one??? Also is not safe trying to flash a ROM from another revice, even if it's basically the same sans few OEM modifications...
---------- Post added at 08:34 PM ---------- Previous post was at 08:32 PM ----------
Assuming you have the XP1929-5 RETBE, the pie firmware would be BECKHAM_PPW29.131_27_1_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml...
Click to expand...
Click to collapse
That is what I am seeing. It is supposed to be upgrade to PPW29.131-27-1.
This firmware works well in my XT-1929-6 (AT&T MX).

SonoranEZR said:
That is what I am seeing. It is supposed to be upgrade to PPW29.131-27-1.
This firmware works well in my XT-1929-6 (AT&T MX).
Click to expand...
Click to collapse
I just don't recommend using ROMs from another places/retails/vendors/etc in your device.... We still don't know what can go wrong as there's barelly any time to test things...

imei
How do you recover imei zerado from the z3 play bike?

I can confirm that it works for European version.
Sent from my Moto Z3 Play using Tapatalk

Already upgraded 3 european Z³ Plays with this and works perfectly on all of them. Didn't lose the IMEI. Just removed those lines that flashes the modem and NON-HLOS.

Vegeta. said:
Hello everyone, I present you how to install Android Pie 9.0.0 stock on your device Moto Z3 Play, remember to follow the indications any doubt write it in the comments please.:
Requirements:
- You can do both with the bootloader blocked and unlocked
- Have ADB and Fastboot installed: https://forum.xda-developers.com/showthread.php?t=2317790
- Have Motorola drivers installed
- Download official Pie 9.0.0 firmware: https://forum.xda-developers.com/z3-play/how-to/android-9-0-pie-rolling-brazil-t3900061/page5 Pag. 5 Post #45
BECKHAM_PPW29.131_27_1_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml
credits to the user @tb110188 for uploading Onedrive
Process:
- Place the device in Bootloader mode connecting the device to the PC waiting for a few seconds to recognize it. After downloading the firmware we will have a folder where in the command console enter:
adb devices
Then adb reboot bootloader which will put the device in bootloader mode
- Enter the command:
fastboot devices to verify that it is recognized by the PC.
then the following:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash 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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot reboot
When entering this last command the device will reboot and show us the initial screen of Android Pie 9.0.0
Notes:
- These commands can be omitted to avoid having problems with the telephone signal (it is unlikely to happen but it is good to prevent)
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
- - This command will erase what is stored in the internal memory of the device, if you want to keep your data omit it
fastboot erase userdata
Click to expand...
Click to collapse
Thank you, I installed Oreo on my Z3 from Germany but I'm in Egypt, it went smooth.
Sent from my [device_name] using XDA-Developers Legacy app

I really wanna do this but I don't know how to backup if anything goes sideways.
My build is clean, no twrp or anything. What should I do first?

iventura said:
I really wanna do this but I don't know how to backup if anything goes sideways.
My build is clean, no twrp or anything. What should I do first?
Click to expand...
Click to collapse
You can backup everything from the main storage to the SD card.
Sent from my [device_name] using XDA-Developers Legacy app

tb110188 said:
Why you flashed, or tried to, the Oreo one??? Also is not safe trying to flash a ROM from another revice, even if it's basically the same sans few OEM modifications...
---------- Post added at 08:34 PM ---------- Previous post was at 08:32 PM ----------
Assuming you have the XP1929-5 RETBE, the pie firmware would be BECKHAM_PPW29.131_27_1_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml...
Click to expand...
Click to collapse
tacochan said:
i've made the same commands as you but i got some errors
D:\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>fastboot flash bluetooth BTFM.bin
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.100s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
D:\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory\BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>fastboot flash dsp dspso.bin
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.380s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command fail
any help?
estoy atorado con unos comandos, me dio estos errores (arriba mencionados), ayudaaa porfa
Click to expand...
Click to collapse
Hi, i have found the souloution. You must set right slot:
fastboot --set-active=a
All partitions has only suffix _a but not __a, you can check it using adb shell:
ls -l /dev/block/platform/soc/c0c4000.sdhci/by-name/
total 0
lrwxrwxrwx 1 root root 21 1970-10-07 08:44 abl_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-10-07 08:44 abl_b -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-10-07 08:44 apdp -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-10-07 08:44 bluetooth_a -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-10-07 08:44 bluetooth_b -> /dev/block/mmcblk0p55
. . . . . and next
[[email protected] Beckhem_9]$ fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.139s]
Finished. Total time: 0.139s
. . . . .
[[email protected] Beckhem_9]$ fastboot flash bluetooth BTFM.bin
Sending 'bluetooth_a' (400 KB) OKAY [ 0.002s]
Writing 'bluetooth_a' OKAY [ 0.013s]
Finished. Total time: 0.016s
[[email protected] Beckhem_9]$ fastboot flash dsp dspso.bin
Sending 'dsp_a' (16384 KB) OKAY [ 0.057s]
Writing 'dsp_a' OKAY [ 0.117s]
Finished. Total time: 0.175s
. . . . . and next
. . . . . and last change
fastboot erase ddr # not DDR
Erasing 'ddr' OKAY [ 0.067s]
Finished. Total time: 0.068s