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
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.
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:
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