so I downloaded a rom the new xperience rom for moto z play and I used it and liked it but wanted to use a different rom well their recovery replaced my twrp so I went to settings and factory reset and now I cant get out of fastboot mode everytime I try it says "start up failed your device didn't start up successfully use the storage repair assistant on computer to repair your device" I think it completely wiped everything my whole sysem I cant even get into twrp so I'm trying to flash twrp and use the back up I have saved on my computer but I get this
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (23420 KB)...
OKAY [ 0.506s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.530s
PLEASE HELP!!!!!!!!!!!
Addison xt1635-02
This is gonna sound stupid. But after you fastboot TWRP, did you try starting ur phone into bootloader, and going to recovery? I thought TWRP wouldn't install at first but it was there all along when I used the English version.
I unlocked the moto-z play. In fastboot it says 'flashing_unlocked'. I tried flashing twrp 3.1.1-addison and I get:
[email protected]:/mnt/hgfs/vmshare# fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (23452 KB)...
OKAY [ 1.613s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.618s
[email protected]:/mnt/hgfs/vmshare
I then tried:
[email protected]:/mnt/hgfs/vmshare# fastboot flash recovery recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16198 KB)...
OKAY [ 1.115s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.313s]
finished. total time: 1.429s
[email protected]:/mnt/hgfs/vmshare#
I downloaded the image three times and all three times I got not signed or corrupt.
Any help here is appreciated.
Y-
use moto fastboot https://forum.xda-developers.com/attachment.php?attachmentid=2427667
The Next time post in Q&A not in development forum
TeamMex said:
use moto fastboot https://forum.xda-developers.com/attachment.php?attachmentid=2427667
The Next time post in Q&A not in development forum
Click to expand...
Click to collapse
Thanks but it failed for me.
[email protected]:/mnt/hgfs/vmshare# ./linux-fastboot flash recovery recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img
target max-sparse-size: 256MB
sending 'recovery' (16198 KB)...
OKAY [ 1.164s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.310s]
finished. total time: 1.474s
[email protected]:/mnt/hgfs/vmshare#
The message that it is not signed out corrupt may be one you need to get used to. As far as I understood: Only Motorola would be capable of signing. But Motorola does not publish any signed does, they only release OTA. At least until now.
Does it work if you just take the message as success?
YileKu said:
Thanks but it failed for me.
[email protected]:/mnt/hgfs/vmshare# ./linux-fastboot flash recovery recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img
target max-sparse-size: 256MB
sending 'recovery' (16198 KB)...
OKAY [ 1.164s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.310s]
finished. total time: 1.474s
[email protected]:/mnt/hgfs/vmshare#
Click to expand...
Click to collapse
More easy
Do
fastboot boot twrname.img
Copy the recovery and flash from the recovery
Note:
If you flash via fastboot you can get these lines but the flash works
Sent from my Motorola Moto Z Play using XDA Labs
tag68 said:
The message that it is not signed out corrupt may be one you need to get used to. As far as I understood: Only Motorola would be capable of signing. But Motorola does not publish any signed does, they only release OTA. At least until now.
Does it work if you just take the message as success?
Click to expand...
Click to collapse
I am unable to access twrp after rebooting the phone, so I assume it didn't actually flash.
With the help of @Nirbhay2 I managed to block my bootloader, however what I wanted to share here is that to block the bootloader of the Brazilian variant it is necessary the last ROM with january security patch POTTER_NPNS25.137-92-4. Here you will find the guide to block your Brazilian device.
Have minimal ADB
Have Motorola drivers installed on your PC
Have the january patch ROM stock: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Extract the ROM to any folder and paste the minimal ADB along with the extracted ROM.
Open a command prompt in the folder and with the device in fastboot mode make a flash of the entire ROM stock on your device, to facilitate copying all the commands at once and paste at the command prompt and it will install automatic to your ROM , then do the same with the commands to re-block the bootloader and at the end of this process your device will be started with bootloader locked.
Commands to re-lock bootloader, do this after the full ROM flash
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
Command link for flash ROM stock
https://pastebin.com/ZWTaWuyr
We thank @Nirbhay2 for this great guide.
I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?
pss34 said:
I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?
Click to expand...
Click to collapse
friend, you need to use this ROM that I made available on the link, if you have a moto G5 plus brazilian you can get the lock, but use this link ROM.
Enviado de meu XT1683 usando Tapatalk
I tried the same thing.
I had TWRP and SuperSu on my phone a few days back. But weirdly, I lost network connectivity and after a botched attempt at installing V4A, the audio died as well. Even the camera and the flash had stopped working. More weirdly, the Root Checker app I had now showed me that root access was not properly installed.
SInce my phone was on the November patch (25-137-92), I found the stock ROM of it online and flashed it with the Moto G5 Plus ToolKit.
Now all the issues I've had are fixed. Everything works perfectly. TWRP has been removed along with SuperSu.
But the bootloader still shows me that software status is modified. The warning on boot-up which tells that the device has been unlocked is still there.
I don't know if it's related but I've got WiFi speed issues now, apps won't download quickly or is it my damn internet?
The bootloader IS locked, though. That I can say confidently because the bootloader unlock option in developer options is now not selected.
Moto G(5) Plus XT1686 4/32 GB Indian Version
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 ?
So I'm having the weirdest issue right now and it's driving me crazy.
I have a Pixel 3a XL. All good. It prompted me about updates for a while and now I had some time to do it.
I grabbed the (title) rom file from Google's site, extracted it and changed "flash-all" so it would not wipe storage. (It's the -w switch).
Like I've done a 100 times already. Nothing fancy, nothing new.
I also removed all images from DCIM and my recordings, etc. So there was like a ton of space on the device when I started.
And yet... I run the script and I get this:
Code:
PS D:\_rom\bonito-sp1a.211105.002> .\flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader' (8377 KB)...
OKAY [ 0.307s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.4-7617386
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.326s]
finished. total time: 0.635s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.051s
target reported max download size of 268435456 bytes
sending 'radio' (73372 KB)...
OKAY [ 1.873s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00129-210806-B-7617386
(bootloader) Flashing partition modem_b
OKAY [ 0.473s]
finished. total time: 2.348s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
error: failed to load 'image-bonito-sp1a.211105.002.zip': Not enough space
Press any key to exit...
PS D:\_rom\bonito-sp1a.211105.002>
I am without a clue and I would really need my device.
Please help?
OS is Windows 11, ADB drivers are from the Google USB package (and fastboot commands go out as you can see so that should be fine).
Not sure what else could be amiss.
Okay, another "self-solved mistery".
I've had the latest platform-tools in my PATH, yet something must have messed it up.
So I ran "flash-all.bat" (while removing -w of course) and then once it gets stuck with "not enough space", I simply run the .exe file directly from the new platform-tools folder, with "update ....zip" and that worked.
Man, every update, something gives me a heart attack.