Good morning, after searching and reading endless post of solutions I did not find any. To if I prepared to post the problem here and see if any solution arises, since we are several affected by this.
I pass the following: When I try to flash firmware stock con ABDtool . First flicks (Prevalidation Failed) Bootloader when flashing:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
It could be caused by not unlocking the boot loader, but My bootloader it unlocked
The bootloader data:
AP Fastoboot Flash Mode (Secure)
BL:80.CB (sha-cfa8344, 2015-11-20 18:51.42)
Baseband: Not found
Product Variant: osprey XT1542 8 GB P2B
Serial Nmber zY2232NR5Q
CPU: MSM8916
eMMC: (GB Micron RV= 06 PV= 12 TY= 17
DRAM: 1024MB Elpida S8 SDRAM DIE= 4GB
Console (NULL): null
Battery Ok
Device is UNLOCKED. Status code 3
Software Status: Modified
Connect USB Data Cable.
You can flash the stock in the same way without flashing those 2 lines, but the terminal lights up and goes straight to Fastboot. Any way to fix it ??
For example I reboot from the Android menu and start in fastboot and I have to press Star to start android.
The ADB commands
fastboot devices
**************
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 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 flash logo logo.bin
If you searched, you would know preflash validation errors mean your device has newer firmware then you are trying to flash. locked devices do no support downgrading, if you can't skip gpt.bin and bootloader.bin and get it booting, you're probably out of luck.
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
Hey, is there anyone using a moto g7 power XT1955-4? If so is it rooted or are you willing/ planning to root it? If yes, then i really need your help. Please let me know if you can help me.
Ballyeet said:
Hey, is there anyone using a moto g7 power XT1955-4? If so is it rooted or are you willing/ planning to root it? If yes, then i really need your help. Please let me know if you can help me.
Click to expand...
Click to collapse
Me bro... See:
xe500linux said:
Whats the difference between fastboot -w and just wiping everything in Twrp? That could have been it.. Syber makes the official Twrp as well so dont know if the one in OP is any different
And theres 4 roms btw, Havoc OS has no thread but its on Syber's androidfilehost. Same rgb/display issues as Lineage though
Click to expand...
Click to collapse
bruh you dont even have to use the fastboot -w or wipe command
CREATOR OF POST: MY F***IN BAD my speak problem was some bs from a blank flash i sorted it now the only bugs i got in some sketchy nav bar
there are apparently these roms as well:
CARBON-CR-7.0-OPAL-UNOFFICIAL-ocean-20191025-1317.zip
Viper-ocean-20191029-v6.7-UNOFFICIAL.zip
XenonHD-191024-Unofficial-ocean.zip
---------- Post added at 09:53 AM ---------- Previous post was at 08:54 AM ----------
FULL GUIDE TO DEBRICK/INSTALL STOCK ROM/REMOVE BAD KEY/INSTALL CUSTOM ROM AND TWRP
ensure your google accounts are removed from the phone and bootloader is unlocked...
boot to bootloader
run cmd prompt
use cd C:\*LOCATION* to go to folder with full STOCK ROM but make sure you have this files in the folder too [adb.exe, fastboot.exe, adbwinapi.dll, adbwinusbapi.dll] from ur minimal adb and fastboot setup. you will also need the recovery file TWRP-ocean-3.3.1-Syber-v2.2_11-02.img in this folder and the logo.bin file to remove the bad key FROM HERE. I suggest you rename to logonew.bin and put in the stock rom folder. you will also want ur RRromzip, the copypartitions.zip, the TWRP INSTALLER, GAPPS & MAGISK ZIP...
no matter what stage u are at other than bricked [after the BLANK FLASH then resume with this guide. if ur stuck bootlooping or have messed anything up start from the stock rom install or you will end up bricking your phone....
ok so in your cmd open in stock rom folder type these commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot-bootloader
when it reboots to bootloader use these commands from the same folder:
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
now use these commands to remove bad key
fastboot flash logo_a logonew.bin
fastboot flash logo_b logonew.bin
now boot the twrp by using
fastboot boot TWRP-ocean-3.3.1-Syber-v2.2_11-02.img
when twrp boots it should show up in ur windows explorer if you have an sd card just drop the files you need on it or you will have to use command adb push copy-partitions-payton.zip /sdcard/
install the copy-partitions-payton.zip
when complete reboot-bootloader
now boot the twrp again by using
fastboot boot TWRP-ocean-3.3.1-Syber-v2.2_11-02.img
now install the rom zip
then the twrp installer zip
reboot-recovery [it auto switches slot]
install gapps and magisk zips
reboot system
you should have ur custom rom and twrp recovery permanently installed now
Thanks for this guide! Does it work with official TWRP?
One more question: I have the RETEU Version, wich zip should i pick? The PPO or the PPOS Version?
thanks in advance!
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]
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?