Related
Hello and thank you for your work, my motorola z2 play came into bootloop from scratch, when it was in stock configuration, then without active debugging usb, bootloader unlocked and being in bootloop I can't unlock anything or even install the official ROM , now I'm trying with Lenovo Moto Smart but I have little hope because the phone keeps turning on and off even when it's in recovery mode. Do you have any advice for me?
Sorry for the poor description but I'm not very experienced, I ask you for advice because I don't know how to do it anymore.
Thank you,
Stephen.
PS: I also tried to unlock the oem with the motorola code but without success
PSS: I copy the account of my tempted to flash the stock rom
>> fastboot flash partition gpt.bin
>> fastboot flash bootloader bootloader.img
>> fastboot flash logo logo.bin
>> fastboot flash boot boot.img
>> fastboot flash recovery recovery.img
>> fastboot flash dsp adspso.bin
>> fastboot flash oem oem.img
>> fastboot flash system system.img_sparsechunk.0
>> fastboot flash system system.img_sparsechunk.1
>> fastboot flash system system.img_sparsechunk.2
>> fastboot flash system system.img_sparsechunk.3
>> fastboot flash system system.img_sparsechunk.4
>> fastboot flash system system.img_sparsechunk.5
>> fastboot flash system system.img_sparsechunk.6
>> fastboot flash system system.img_sparsechunk.7
>> fastboot flash 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
OKAY [ 0.002s]
Finished. Total time: 0.007s
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.166s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.281s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo: not found
Sending 'logo' (2192 KB) OKAY [ 0.214s]
Writing 'logo' OKAY [ 0.066s]
Finished. Total time: 0.430s
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.547s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.639s]
Writing 'recovery' (bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logicalem: not found
Sending 'oem' (232923 KB) OKAY [ 5.260s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Sending 'system' (517135 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (506931 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (522215 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (521087 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (518083 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (515569 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (250209 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
fastboot: error: cannot load 'system.img_sparsechunk.7': No such file or directory
(bootloader) is-logical:modem: not found
Sending 'modem' (75092 KB) OKAY [ 1.821s]
Writing 'modem' OKAY [ 0.807s]
Finished. Total time: 2.731s
Erasing 'modemst1' OKAY [ 0.028s]
Finished. Total time: 0.032s
Erasing 'modemst2' OKAY [ 0.028s]
Finished. Total time: 0.032s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2932 KB) OKAY [ 0.230s]
Writing 'fsg' OKAY [ 0.086s]
Finished. Total time: 0.336s
Erasing 'cache' OKAY [ 0.006s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.277s]
Finished. Total time: 0.281s
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.132s]
Finished. Total time: 0.135s
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.004s
"Update"
I tried to use Lenovo moto smart assistant and the result is this message:
Start Up Failed:
Your devices didn't start up successfully.
Use the software repair assistant on computer to repair your devices.
Connect your device[...]
Ap Fastboot Flash Mode (Secure)
ERROR: Failed topass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
USB connected
thank you guys!
Could you find any solution?
stemonta said:
Hello and thank you for your work, my motorola z2 play came into bootloop from scratch, when it was in stock configuration, then without active debugging usb, bootloader unlocked and being in bootloop I can't unlock anything or even install the official ROM , now I'm trying with Lenovo Moto Smart but I have little hope because the phone keeps turning on and off even when it's in recovery mode. Do you have any advice for me?
Sorry for the poor description but I'm not very experienced, I ask you for advice because I don't know how to do it anymore.
Thank you,
Stephen.
PS: I also tried to unlock the oem with the motorola code but without success
PSS: I copy the account of my tempted to flash the stock rom
>> fastboot flash partition gpt.bin
>> fastboot flash bootloader bootloader.img
>> fastboot flash logo logo.bin
>> fastboot flash boot boot.img
>> fastboot flash recovery recovery.img
>> fastboot flash dsp adspso.bin
>> fastboot flash oem oem.img
>> fastboot flash system system.img_sparsechunk.0
>> fastboot flash system system.img_sparsechunk.1
>> fastboot flash system system.img_sparsechunk.2
>> fastboot flash system system.img_sparsechunk.3
>> fastboot flash system system.img_sparsechunk.4
>> fastboot flash system system.img_sparsechunk.5
>> fastboot flash system system.img_sparsechunk.6
>> fastboot flash system system.img_sparsechunk.7
>> fastboot flash 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
OKAY [ 0.002s]
Finished. Total time: 0.007s
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.166s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.281s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo: not found
Sending 'logo' (2192 KB) OKAY [ 0.214s]
Writing 'logo' OKAY [ 0.066s]
Finished. Total time: 0.430s
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.547s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.639s]
Writing 'recovery' (bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logicalem: not found
Sending 'oem' (232923 KB) OKAY [ 5.260s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Sending 'system' (517135 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (506931 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (522215 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (521087 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (518083 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (515569 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (250209 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
fastboot: error: cannot load 'system.img_sparsechunk.7': No such file or directory
(bootloader) is-logical:modem: not found
Sending 'modem' (75092 KB) OKAY [ 1.821s]
Writing 'modem' OKAY [ 0.807s]
Finished. Total time: 2.731s
Erasing 'modemst1' OKAY [ 0.028s]
Finished. Total time: 0.032s
Erasing 'modemst2' OKAY [ 0.028s]
Finished. Total time: 0.032s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2932 KB) OKAY [ 0.230s]
Writing 'fsg' OKAY [ 0.086s]
Finished. Total time: 0.336s
Erasing 'cache' OKAY [ 0.006s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.277s]
Finished. Total time: 0.281s
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.132s]
Finished. Total time: 0.135s
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.004s
"Update"
I tried to use Lenovo moto smart assistant and the result is this message:
Start Up Failed:
Your devices didn't start up successfully.
Use the software repair assistant on computer to repair your devices.
Connect your device[...]
Ap Fastboot Flash Mode (Secure)
ERROR: Failed topass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
USB connected
thank you guys!
Click to expand...
Click to collapse
Can u tell me your model [email protected]
Good evening everyone, I introduce myself my name is Eduardo de Mexíco, I want to contribute to help people who have problems with the Moto Z2 Force.
I have the Model XT1789-5, first unlock the bootloader with Motorola and upgrade to Android Pie.
Now I don't have IME, baseband and WIfi.
I have read a lot in this forum, but I cannot find the correct repair.
That's why I put this thread in order to give a repair to my cell phone.
Attach the "flash" with minimal ADB and fastbool tool.
Is the emmc damaged?
The blanck flash appears "waiting for devices" I have installed Motorola and Qualcomm drivers.
I can't change firmware.
Can you help me, please?
Microsoft Windows [Versión 10.0.17763.678]
(c) 2018 Microsoft Corporation. Todos los derechos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Already locked
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.011s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.233s]
finished. total time: 0.248s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.209s]
finished. total time: 0.518s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (97407 KB)...
OKAY [ 2.885s]
writing 'modem_a'...
OKAY [ 1.040s]
finished. total time: 3.929s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.173s]
writing 'fsg_a'...
OKAY [ 0.067s]
finished. total time: 0.247s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.006s]
finished. total time: 0.008s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bluetooth BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.055s]
finished. total time: 0.199s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.487s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.646s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.111s]
writing 'logo_a'...
OKAY [ 0.042s]
finished. total time: 0.157s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23345 KB)...
OKAY [ 0.693s]
writing 'boot_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.878s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.095s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.151s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 15.404s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.449s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.299s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.342s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.112s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.163s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 15.335s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.386s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (413387 KB)...
OKAY [ 12.137s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 12.182s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system_b system_b.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.059s]
writing 'system_b'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.106s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system_b system_b.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (319601 KB)...
OKAY [ 9.336s]
writing 'system_b'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 9.377s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (163069 KB)...
OKAY [ 4.820s]
writing 'oem_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.862s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.765s]
finished. total time: 0.771s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase ddr
erasing 'ddr'...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
I can't install the TWRP
I currently have the OPXS version 27.109-34-21 With this firmware it worked fine, but not now.
Beforehand
Thank you!!
You flashed pie, you can't go back to oreo, so you have to flash pie again. Since you have no baseband or imei, you must have flashed the wrong variant. Who is your provider, what was your software channel originally? What is the package name of the OREO firmware that worked for you in the past. This information will help determine what you need to flash in order to repair. Why is everyone obsessed with locking the bootloader? When you lock your bootloader, you dramatically reduce the options and tools available to fix your phone when things go wrong.
XDA Developers The BEST!!!
41rw4lk said:
You flashed pie, you can't go back to oreo, so you have to flash pie again. Since you have no baseband or imei, you must have flashed the wrong variant. Who is your provider, what was your software channel originally? What is the package name of the OREO firmware that worked for you in the past. This information will help determine what you need to flash in order to repair. Why is everyone obsessed with locking the bootloader? When you lock your bootloader, you dramatically reduce the options and tools available to fix your phone when things go wrong.
Click to expand...
Click to collapse
41rw4lk
* 41rw4lk
* 41rw4lk
You're the best!!!!!
Thank you!!!! IT WORKED!!!
Thanks for your support!!!!!!
I have IME, Baseband, all normal.
I got an update to PIE is the collection no. PPX29-159-23
I DIDN'T download it.
If I can download it?
regards
If everything is working normally, and you received an ota notification to update, then you should be able to update just fine. If it's some random firmware you came across, I wouldn't.
Pie
Hi good day.
I can't update Android Pie.
Tells me
Incorrect software update
My channel is OPMX.
The phone is company free
What I did was install the NASH RETAIL OPXS27 109 34 21 Firmware, this is what I had.
Then by fastboot install the NASH RETAIL PPX29 159 23 update.
But it is not updated, what can I do.
Recover the IMEI baseband and the phone works well.
lalo74 said:
Hi good day.
I can't update Android Pie.
Tells me
Incorrect software update
My channel is OPMX.
The phone is company free
What I did was install the NASH RETAIL OPXS27 109 34 21 Firmware, this is what I had.
Then by fastboot install the NASH RETAIL PPX29 159 23 update.
But it is not updated, what can I do.
Recover the IMEI baseband and the phone works well.
Click to expand...
Click to collapse
So just to confirm, everything is working on Retail pie right now yes?
Originally, you were on OpenMX firmware, and your software channel was/and is still OPMX yes?
Can you take a screenshot of the update being offered? OpenMX doesn't have pie yet, so if that is the update being offered then it will fail because you're on Retail firmware. So If you want to go back to OpenMX then we need to do a few things and it has to be a pie update being offered. Otherwise, you can update using any new Retail releases. Not Retin, Rebr, etc. Just plain Retail and you have the latest right now.
Pie
Hello
Thanks for your prompt response
It is currently in the openmix channel.
Before I was on the openmix channel the same.
The firmware was RETAIL.
So it was before the bootloader and flash unlock.
Now he is working fine without problems with
Openmix
NASH RETAIL Opxs27 109 34 21
I attach images
Can you help me please upgrade to Pie.
Photo
Good afternoon 41rw4lk
Look how is my phone
The firmware you download is this
NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml[IMG
https://ibb.co/7XM0t5Z
https://ibb.co/PC5dVs6
Good afternoon 41rw4lk
Look how is my phone
The firmware you download is this
NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
nash/official/RETAIL/NASH_RETAIL_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but it was not installed
What is the correct procedure to update again and what are the commands for the firmware through minimal ADB Fastboot tool
https://ibb.co/v1Jx5Mq
https://ibb.co/q7P5spt
https://ibb.co/34ZFnWZ
https://ibb.co/KmcGKY0
https://ibb.co/vjx9rwR
firmware
Do I install this version?
NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Hold on, we need to check a couple of things because I'm confused.
In your OP you mentioned pie upgrade, did you ever upgrade to pie at all? The reason I ask is because in your photo you're running oreo, which would leave you without a baseband if you upgraded to pie modems.
Long story short, if everything is working (mobile data, wifi, bluetooth) etc. Then you should enable oem unlocking and adb debugging and unlock your bootloader again if you haven't already. An unlocked bootloader won't stop otas, it just gives you more options to flash and fix your phone, plus if you want twrp and/or root you'll need to be unlocked.
This is the firmware you flashed to get oreo running on your phone currently right? NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Option A - If you flashed that Retail firmware and all is well. I would flash this firmware to upgrade to pie. You won't be able to take otas since your channel is OPMX, but you will have pie without any bloat.
Option B - As of now, there is no OpenMX pie firmware on lolinet, but it looks like that's the update being offered since you have OPMX as your software channel and from the photo you posted. So if you want proper OpenMX and the ability to take otas, you'll need to flash back to an OpenMX firmware then take your ota.
I would unlock your bootloader before anything, that way if anything goes wrong you have options. Don't flash any pie firmware until you know what you need. If you are unsure, ask questions. Pie isn't the friendliest firmware to flash and will cause problems if you flash the wrong variant.
Command
Good night 41rw4lk
The problem I think are the commands
First
I had this firmware NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml OK installed.
What I did was unlock the bootloader, with the steps of a YouTube video https://www.youtube.com/watch?v=cXxr-Y1ozSY
Then I updated Pie with this firmware Moto/nash/official/RETAIL/NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It did not work. Back to the firmware of OREO OPXS27 109 34 21, this is where I no longer had the bace band NO IME no Wifi etc.
I was researching for a week ... but nothing worked. The OEM key did not respond, now it responds. I had the pleasure and miracle of meeting you and you tell me:
Go back to the firmware you had.
I do it and then upgrade to PIE PPX29 159 23 and it doesn't work.
Then I turn on the cell phone with OREO OPXS27 109 34 21 and IF the IMEI works the baseband and the Wifi.
Through OTA I get the update message, which is not installed.
Errors The commands I use to flash the firmware.
Now I am watching a YouTube video where they explain how to use the correct commands for each Firmware. What do you think?
The bad thing is that it is in Spanish
https://www.youtube.com/watch?v=a5PwF-qlAVc
What are the correct commands to update the firmware?
I will not flash until I agree with you.
Regards!!
I feel like we're going around in circles lol.
Does your phone work correctly right now? Does it have mobile signal and data, wifi, bluetooth etc?
If it does, what is the full name of the firmware you used to put it in working order?
41rw4lk said:
I feel like we're going around in circles lol.
Does your phone work correctly right now? Does it have mobile signal and data, wifi, bluetooth etc?
If it does, what is the full name of the firmware you used to put it in working order?
Click to expand...
Click to collapse
Hi good day
That's how the phone is working well; It has Wifi signal, IME, base band works 100%.
The firmware I am with now is:
NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
To flash, subject to your opinion I have this procedure:
Phone
Activate Android programmer
Activate OEM
Enable USB debugging
Activate flash mode Moto Z2 (volume - and power button)
Computer:
ADB minimal tool v1.43
In the adb folder install the fimware and extract rar files.
NASH_RETAIL_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
In the cmd window write
flashboot deivices
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 bluetooth flash BTFM.bin
fastboot flash dsp adspso.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 system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot reboot
As time?
How about?
Regards!!
This is your current firmware right? NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
But when you flash NASH_RETAIL_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip you lose baseband and imei?
If your bootloader isn't unlocked, I would unlock it so that you have some wiggle room if something goes wrong. With a locked bootloader you can only flash official signed, same version or higher, and that's not guaranteed.
As far as your flashing commands, it is best to use the preparation.bat from this thread to generate your own flashall for the firmware you have. Since we have different variants if you're not careful a flashall that you pickup around here might not flash everything you need to flash. So generate your own to be certain.
hello friends, i have a problem, i have a z2 force, with android 8.0.0, retbr software channel, security patch from january 1, 2018, installed version number is opxs27.109-34-4.
In fastboot mode I have baseband not found, I have BL: MBM-3.0-nash_retail-641a15b-180105, in product and variant I have: Nash radio2 64GB PVT and lastly I have Flashing_locked, can anyone help me with which firmware I can try to recover the cell phone ?
Hi, Have an MOTO G 5 XT 1672 In inifinity loop, he has oem_locked,
in fastboot mode i select recovery mode and shows logo and loop again, don't give me the option "no command" for wipe data. Tried the Lenovo Rescue and Smart Assistant, she find the smartphone, flash the system and give me success, but the phone shows nothing different. He continues loop in boot logo.
Tried manually with ADB with the actual firmware and comands lines but no success too. i dont know what to do.
If someone give me an light i will apreciate.
welitonxdd said:
Hi, Have an MOTO G 5 XT 1672 In inifinity loop, he has oem_locked,
in fastboot mode i select recovery mode and shows logo and loop again, don't give me the option "no command" for wipe data. Tried the Lenovo Rescue and Smart Assistant, she find the smartphone, flash the system and give me success, but the phone shows nothing different. He continues loop in boot logo.
Tried manually with ADB with the actual firmware and comands lines but no success too. i dont know what to do.
If someone give me an light i will apreciate.
Click to expand...
Click to collapse
Does it give any error, when flashing the stock Oreo. Like permission denied for erase user data or any other?
welitonxdd said:
Hi, Have an MOTO G 5 XT 1672 In inifinity loop, he has oem_locked,
in fastboot mode i select recovery mode and shows logo and loop again, don't give me the option "no command" for wipe data. Tried the Lenovo Rescue and Smart Assistant, she find the smartphone, flash the system and give me success, but the phone shows nothing different. He continues loop in boot logo.
Tried manually with ADB with the actual firmware and comands lines but no success too. i dont know what to do.
If someone give me an light i will apreciate.
Click to expand...
Click to collapse
In fastboot mode type the following
fastboot erase userdata
This is the equivalent of doing a factory reset - all data will be erased including anything on internal storage
Without a full hardware/software diagnosis of your phone there really isn't anything else to suggest
riyan65 said:
Does it give any error, when flashing the stock Oreo. Like permission denied for erase user data or any other?
Click to expand...
Click to collapse
No error, give me success, but nothing happens
TheFixItMan said:
In fastboot mode type the following
fastboot erase userdata
This is the equivalent of doing a factory reset - all data will be erased including anything on internal storage
Without a full hardware/software diagnosis of your phone there really isn't anything else to suggest
Click to expand...
Click to collapse
i made this but nothing happens, i have no idea what to do now see video
youtube
watch?v=4apyEzljmjA
welitonxdd said:
No error, give me success, but nothing happens
i made this but nothing happens, i have no idea what to do now see video
youtube
watch?v=4apyEzljmjA
Click to expand...
Click to collapse
It looks like you have no rom installed either due to flashing wrong firmware or incomplete flashing or you have a hardware fault
Download firmware from below - make sure it's the same android version as you currently have eg android 7 or 8
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Commands to use
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Post output - note if you get security downgrade error flashing gpt or bootloader the firmware is too old
If you get permission denied try a different firmware as your device does not have an unlocked bootloader you can't flash unsigned firmware parts
TheFixItMan said:
Post output - note if you get security downgrade error flashing gpt or bootloader the firmware is too old
If you get permission denied try a different firmware as your device does not have an unlocked bootloader you can't flash unsigned firmware parts
Click to expand...
Click to collapse
before I had done it this way, without success too, now that I tried again this option of "is logical not found" appears, but even with this option it seems that the command has tried several firmwares but the one that does not give the mentioned error is last one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D:\adbmoto>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.171s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.091s]
Finished. Total time: 0.286s
D:\adbmoto>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.499s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.555s]
Finished. Total time: 1.075s
D:\adbmoto>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2242 KB) OKAY [ 0.478s]
Writing 'logo' OKAY [ 0.100s]
Finished. Total time: 0.608s
D:\adbmoto>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 1.710s]
Writing 'boot' OKAY [ 0.430s]
Finished. Total time: 2.177s
D:\adbmoto>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 1.316s]
Writing 'recovery' OKAY [ 0.441s]
Finished. Total time: 1.779s
D:\adbmoto>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 1.477s]
Writing 'dsp' OKAY [ 0.282s]
Finished. Total time: 1.803s
D:\adbmoto>fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (148900 KB) OKAY [ 4.891s]
Writing 'oem' OKAY [ 7.660s]
Finished. Total time: 21.190s
D:\adbmoto>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (258344 KB) OKAY [ 8.377s]
Writing 'system' OKAY [ 5.902s]
Finished. Total time: 17.582s
D:\adbmoto>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256570 KB) OKAY [ 8.307s]
Writing 'system' OKAY [ 5.519s]
Finished. Total time: 17.536s
D:\adbmoto>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (246510 KB) OKAY [ 8.012s]
Writing 'system' OKAY [ 6.545s]
Finished. Total time: 19.623s
D:\adbmoto>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 8.472s]
Writing 'system' OKAY [ 7.533s]
Finished. Total time: 19.463s
D:\adbmoto>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (261322 KB) OKAY [ 8.451s]
Writing 'system' OKAY [ 11.216s]
Finished. Total time: 24.197s
D:\adbmoto>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 8.481s]
Writing 'system' OKAY [ 5.513s]
Finished. Total time: 17.029s
D:\adbmoto>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (262143 KB) OKAY [ 8.489s]
Writing 'system' OKAY [ 6.678s]
Finished. Total time: 19.322s
D:\adbmoto>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (256817 KB) OKAY [ 8.302s]
Writing 'system' OKAY [ 6.812s]
Finished. Total time: 20.305s
D:\adbmoto>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (237909 KB) OKAY [ 7.713s]
Writing 'system' OKAY [ 7.424s]
Finished. Total time: 18.200s
D:\adbmoto>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (66358 KB) OKAY [ 2.278s]
Writing 'modem' OKAY [ 1.050s]
Finished. Total time: 5.473s
D:\adbmoto>fastboot erase modemst1
Erasing 'modemst1' OKAY [ 0.035s]
Finished. Total time: 0.041s
D:\adbmoto>fastboot erase modemst2
Erasing 'modemst2' OKAY [ 0.036s]
Finished. Total time: 0.041s
D:\adbmoto>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2956 KB) OKAY [ 0.440s]
Writing 'fsg' OKAY [ 0.119s]
Finished. Total time: 0.589s
D:\adbmoto>fastboot erase cache
Erasing 'cache' OKAY [ 0.009s]
Finished. Total time: 0.014s
D:\adbmoto>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.176s]
Finished. Total time: 0.183s
D:\adbmoto>fastboot oem fb_mode_clear
OKAY [ 0.002s]
Finished. Total time: 0.004s
D:\adbmoto>fastboot reboot
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.004s
D:\adbmoto>
Click to expand...
Click to collapse
welitonxdd said:
before I had done it this way, without success too, now that I tried again this option of "is logical not found" appears, but even with this option it seems that the command has tried several firmwares but the one that does not give the mentioned error is last one
Click to expand...
Click to collapse
There's no errors in the output and everything is normal
Although unlikely to be causing an issue remove any sdcard and sim card from the device & try to boot
If it's still not booting after you have left it trying to boot for a while you may have a hardware fault
There's not really anything I can suggest - you can try using a different fastboot
Try using the mfastboot in the attachment below
Copy firmware to same directory as mfastboot
The commands are the same as above but instead of typing fastboot before each command type mfastboot
TheFixItMan said:
There's no errors in the output and everything is normal
Although unlikely to be causing an issue remove any sdcard and sim card from the device & try to boot
If it's still not booting after you have left it trying to boot for a while you may have a hardware fault
There's not really anything I can suggest - you can try using a different fastboot - I'll upload it in a min
Click to expand...
Click to collapse
the procediments was made without SIM and SD cards. i think the only answers now is the hardware fault.
thanks for your attention. and response in my topic.
welitonxdd said:
the procediments was made without SIM and SD cards. i think the only answers now is the hardware fault.
thanks for your attention. and response in my topic.
Click to expand...
Click to collapse
Try with the mfastboot I just posted in post above just incase the version you're using has issues - just substitute fastboot for mfastboot in the commands
TheFixItMan said:
Try with the mfastboot I just posted in post above just incase the version you're using has issues - just substitute fastboot for mfastboot in the commands
Click to expand...
Click to collapse
I finished now, the last hope was this, I did the procedure and it was the same way, after resetting it stays in the loop
welitonxdd said:
I finished now, the last hope was this, I did the procedure and it was the same way, after resetting it stays in the loop
Click to expand...
Click to collapse
Assuming you have tried the generic retail firmware there's not really anything else I can suggest
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
TheFixItMan said:
Assuming you have tried the generic retail firmware there's not really anything else I can suggest
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Yeah, already made with this firmware, the only accepted.
Strange is dont pass into recovery mode after fastboot screen. hardware fault sucks...
Another information is in Lenovo Smart Assistant continues showing RETBR, ive flashed only retail original
Notice there is a huge issue with the modem in another post https://forum.xda-developers.com/z2-force/help/0-imei-pie-xt-1789-03-sprint-t3957851 please stay tune
I am having an issue with Wifi, I attempted to update lineage os 17.1 did process to clean flash. After did all the process provided with the guide of lineage os official wiki of my moto Z2 when it booted it got stuck on the loop lineage logo for over 15 minutes than usual with it configures. I decided to flash it back to stock, did a script for it of course(using an example of rcmaehl here XDA) due to long periods test fail I was able to boot it in stock oreo, but when I got to set it up, it does not show any wifi and not even data of carrier. went to the bootloader again to notice that broadband is unknown(not found). long story short I have a half soft brick phone. Any idea and suggestion.
The script I was able to make flash to stock oreo:
Code:
@echo off
adb reboot bootloader
fastboot --set-active=a
ECHO Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to rebooting to flash to B.
pause
adb reboot bootloader
pause
adb --set-active=b
echo Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to reboot.
pause
fastboot reboot
Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.
41rw4lk said:
Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.
Click to expand...
Click to collapse
I attempted as avised with script convertor of RootJunky. First attempt running the script
Code:
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.000s]
Finished. Total time: 0.000s
(bootloader) is-logical:partition: not found
Sending 'partition' (206 KB) OKAY [ 0.016s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.185s]
Finished. Total time: 0.216s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.331s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.169s]
Finished. Total time: 0.501s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (97431 KB) ^CTerminate batch job (Y/N)? n
Sending 'fsg' (5596 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.135s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.594s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (3151 KB) OKAY [ 0.085s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (23357 KB) OKAY [ 0.721s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516201 KB) OKAY [ 16.038s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (495129 KB) OKAY [ 15.564s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (519125 KB) OKAY [ 16.524s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523779 KB) OKAY [ 16.152s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516309 KB) OKAY [ 16.016s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (420583 KB) OKAY [ 13.061s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system_b: not found
Sending 'system_b' (515183 KB) OKAY [ 16.010s]
Writing 'system_b' OKAY [ 2.907s]
Finished. Total time: 25.177s
(bootloader) is-logical:system_b: not found
Sending 'system_b' (307220 KB) OKAY [ 9.615s]
Writing 'system_b' OKAY [ 1.648s]
Finished. Total time: 14.835s
(bootloader) is-logical:oem__a: not found
Sending 'oem__a' (175682 KB) OKAY [ 5.476s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'modemst2' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'carrier' OKAY [ 0.001s]
Finished. Total time: 0.004s
Erasing 'cache' OKAY [ 0.000s]
Finished. Total time: 0.004s
Erasing 'userdata' OKAY [ 0.075s]
Finished. Total time: 0.082s
Erasing 'ddr' OKAY [ 0.001s]
Finished. Total time: 0.006s
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5596 KB) OKAY [ 0.173s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.137s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.001s]
Finished. Total time: 0.004s
I notice the error, then proceeded to fix which it should be flash. all it flashes well, but went attempt to reboot to see if system boots up and go back to bootloader .
I'm aware that my scripting is the worst:laugh:, but funny part it got the job done to able to see the system up and running of course without data or wifi connection. :silly: I do appreciate the assistance and Hopefully keep having the assist with suggestions or guides of course. thankfully I have back up the phone(Not Moto z2) but really wish to go back this phone to able to use it as my main again...
If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.
it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?
insanegrim said:
it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?
Click to expand...
Click to collapse
Go back to fastboot and flash the modem only.
fastboot flash modem (drag and drop the NON-HLOS.bin from your firmware here)
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
If that doesn't work it may be possible that your persist partition is full and not letting the modem initialize. You'll need root for this.
adb shell
su
cd /mnt/vendor/persist/cache/recovery
rm log
rm last_log
exit
exit
adb reboot
41rw4lk said:
If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.
Click to expand...
Click to collapse
This soft bricked and now it bootloops my xt1789-04
If your output looks like this do the following.
Code:
sending 'modema' (65420 KB)...
OKAY [ 1.495s]
writing 'modema'...
(bootloader) Invalid partition name modema
FAILED (remote failure)
finished. total time: 1.525s
target reported max download size of 536870912 bytes
sending 'fsga' (9192 KB)...
OKAY [ 0.213s]
writing 'fsga'...
(bootloader) Invalid partition name fsga
FAILED (remote failure)
finished. total time: 0.232s
target reported max download size of 536870912 bytes
sending 'dspa' (16384 KB)...
OKAY [ 0.378s]
writing 'dspa'...
(bootloader) Invalid partition name dspa
FAILED (remote failure)
finished. total time: 0.393s
target reported max download size of 536870912 bytes
sending 'logoa' (1285 KB)...
OKAY [ 0.034s]
writing 'logoa'...
(bootloader) Invalid partition name logoa
FAILED (remote failure)
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'boota' (32768 KB)...
OKAY [ 0.820s]
writing 'boota'...
(bootloader) Invalid partition name boota
FAILED (remote failure)
finished. total time: 0.834s
You need to specify the A/B partitions like the following. Just add "_" to the Invalid partition name.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg_a fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit