Good news, motorola anounced the July update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I don't know the delay but today in August 1 the update is available
I got my device in May and already recieved the June update, so it's not the first for me.
But I believe one vision was released later (June) for some regions.
luisjoseb said:
Good news, motorola publishied the first update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I will update the post when this come to the device!!!
Click to expand...
Click to collapse
Do you know if this update solve the bootloop caused by enable fingerprint along with developer option ?
AndresOrue said:
Do you know if this update solve the bootloop caused by enable fingerprint along with developer option ?
Click to expand...
Click to collapse
Awaiting the update. But I don't think what you have described is the actual issue. I have fingerprint and developer options enabled and the device works just fine.
From what I have read, the issue is fingerprint + changing the default USB configuration. Isn't it?
baunthiyal said:
Awaiting the update. But I don't think what you have described is the actual issue. I have fingerprint and developer options enabled and the device works just fine.
From what I have read, the issue is fingerprint + changing the default USB configuration. Isn't it?
Click to expand...
Click to collapse
I changed that setting the first time and the phone enter in a bootloop and because I had to reset everything, I didn't try again . In this moment, I have developer option enable and the fingerprint disable.
AndresOrue said:
I changed that setting the first time and the phone enter in a bootloop and because i had to reset everything, I didn't try again . In this moment i have developer option enable and the fingerprint disable.
Click to expand...
Click to collapse
Here's my journey with Vision as of now -
1. Got this phone last week
2. Added fingerprints
3. Updated to PSA29.137-17
4. Enabled developer options
5. Changed all animation rates in developer options to 0.5
I'm not sure you should try steps 1-4. But personally, I didn't have the issue you have described.
baunthiyal said:
Here's my journey with Vision as of now -
1. Got this phone last week
2. Added fingerprints
3. Updated to PSA29.137-17
4. Enabled developer options
5. Changed all animation rates in developer options to 0.5
I'm not sure you should try steps 1-4. But personally, I didn't have the issue you have described.
Click to expand...
Click to collapse
Thanks mate. I enabled fingerprint and developer option and it works. Seems that the problem was what You said, enable fingerprint and changing the default USB configuration.
i just installed this update and after i checked the app for new android update it told me:
integrity system corrupted
You will not be able to get any future updates.
Go to the store and official rom will be installed
Something like this .. Do you see this aswell?
I have bought my one vision the day it became available in my country, June 3rd, I have April's security patch and nothing to update, is there any other security patch available?
ᕙ(⇀‸↼)ᕗ said:
i just installed this update and after i checked the app for new android update it told me:
integrity system corrupted
You will not be able to get any future updates.
Go to the store and official rom will be installed
Something like this .. Do you see this aswell?
Click to expand...
Click to collapse
This is normal with bootloader unlocked.
View attachment 4793287
xt1970-3 touch not working
i got a xt1970-3 from customer and touch is not working, i tried to flash with fastboot " XT1970-3_KANE_RETEU_9.0_PSA29.137-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" the same version in phone, i flashed logo.bin, boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.2, system.img_sparsechunk.3, system.img_sparsechunk.4, system.img_sparsechunk.5, system.img_sparsechunk.6, system.img_sparsechunk.7, system.img_sparsechunk.8, system.img_sparsechunk.9, system.img_sparsechunk.10, system_other.img_sparsechunk.0, system_other.img_sparsechunk.1, system_other.img_sparsechunk.2,
and now phone in bootloop mode, please i want to known how to flash this again
rizni said:
i got a xt1970-3 from customer and touch is not working, i tried to flash with fastboot " XT1970-3_KANE_RETEU_9.0_PSA29.137-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" the same version in phone, i flashed logo.bin, boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.2, system.img_sparsechunk.3, system.img_sparsechunk.4, system.img_sparsechunk.5, system.img_sparsechunk.6, system.img_sparsechunk.7, system.img_sparsechunk.8, system.img_sparsechunk.9, system.img_sparsechunk.10, system_other.img_sparsechunk.0, system_other.img_sparsechunk.1, system_other.img_sparsechunk.2,
and now phone in bootloop mode, please i want to known how to flash this again
Click to expand...
Click to collapse
This is how I flash full firmware without wiping userdata.
Code:
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.nbl1.bin
fastboot flash ldfw_a ldfw.bin
fastboot flash ldfw_b ldfw.bin
fastboot flash keystorage_a keystorage.bin
fastboot flash keystorage_b keystorage.bin
fastboot flash bootloader_a bootloader.bin
fastboot flash bootloader_b bootloader.bin
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
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_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot fastboot flash vendor_a vendor.img
If you want to wipe userdata you could just add "fastboot erase userdata" at the end.
If that won't work it's probably broken digitizer or something.
thank you for quick guide, the phone is on now but the touch not working, it must be something to do with hardware
thank you
luisjoseb said:
Good news, motorola anounced the July update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I don't know the delay but today in August 1 the update is available
Click to expand...
Click to collapse
I got the update yesterday
wtf
tys0n said:
This is normal with bootloader unlocked.
View attachment 4793287
Click to expand...
Click to collapse
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
ᕙ(⇀‸↼)ᕗ said:
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
Click to expand...
Click to collapse
There is no update for me
And Google Duo not work
ed.shevsky said:
There is no update for me
And Google Duo not work
Click to expand...
Click to collapse
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
ᕙ(⇀‸↼)ᕗ said:
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
Click to expand...
Click to collapse
Sorry, my fault. My phone is locked, so I don't need to flash boot.img
May be you know a method to force OTA update?
And about Google Duo. The program stop working after Play Market version updated. Once I fix it by factory reset. But I don't want do it every time
ᕙ(⇀‸↼)ᕗ said:
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
Click to expand...
Click to collapse
Ok nice. Still didn't work for me but I'm flashing it with fastboot now instead.
ᕙ(⇀‸↼)ᕗ said:
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
Click to expand...
Click to collapse
Did you also get error about "too many links" when trying to flash magisk patched boot?
Related
Dear all,
after a try to load the Chinese twp and root my z play I bricked my phone. Now the only think that I can get is fast boot screen that says:
bl:co.14
baseband: not found
product: xt1635-02 32gb p7
serial number:
.
.
.
flashing_unlocked
.
.
I am trying to load the XT1635-02_ADDISON_RETUS_6.0.1_MPNS24.104-49-4 firmware by running a bat file that I found somewhere around with the following commands:
echo off
fastboot getvar max-sparse-size
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase DDR
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
But I get a screen says erasing... and the boot loop!!!
ANY IDEAS GUYS??
thx in advance for your help!!!:crying::crying::crying::crying:
asprofridis said:
Dear all,
after a try to load the Chinese twp and root my z play I bricked my phone. Now the only think that I can get is fast boot screen that says:
bl:co.14
baseband: not found
product: xt1635-02 32gb p7
serial number:
.
.
.
flashing_unlocked
.
.
I am trying to load the XT1635-02_ADDISON_RETUS_6.0.1_MPNS24.104-49-4 firmware by running a bat file that I found somewhere around with the following commands:
echo off
fastboot getvar max-sparse-size
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase DDR
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
But I get a screen says erasing... and the boot loop!!!
ANY IDEAS GUYS??
thx in advance for your help!!!:crying::crying::crying::crying:
Click to expand...
Click to collapse
Just flash the boot.img, recovery.img , all sparsechunks.img and the OEM.img using fastboot.
After you've flashed type in fastboot erase userdata and then fastboot reboot and see what happens
Sent from my XT1635-02 using XDA-Developers Legacy app
---------- Post added at 09:25 PM ---------- Previous post was at 09:23 PM ----------
You should never flash using a short cut or a bat file found in some obscure thread or website
Sent from my XT1635-02 using XDA-Developers Legacy app
Is the device recognized by fastboot?
Command: fastboot devices
Guys, I have a similar problem.
After an update of the android give error, I can no longer connect my moto z play.
Nor in fastboot and adb enters.
See video:
http://youtu.be/o8yYn0hNers
Luiz_Pennywise said:
Guys, I have a similar problem.
After an update of the android give error, I can no longer connect my moto z play.
Nor in fastboot and adb enters.
See video:
http://youtu.be/o8yYn0hNers
Click to expand...
Click to collapse
Oh man, the same problem here. I was updating the android for N and when restart the phone doesn't turn on, I'm crazy because I don't find anything to fix :crying::crying::crying::crying:
Luiz_Pennywise said:
Guys, I have a similar problem.
After an update of the android give error, I can no longer connect my moto z play.
Nor in fastboot and adb enters.
See video:
http://youtu.be/o8yYn0hNers
Click to expand...
Click to collapse
kaue152 said:
Oh man, the same problem here. I was updating the android for N and when restart the phone doesn't turn on, I'm crazy because I don't find anything to fix :crying::crying::crying::crying:
Click to expand...
Click to collapse
Have you guys downgraded to Marshmallow, then tried updating to N again? Particularly after installing the April update?
IncendiaryPyro said:
Have you guys downgraded to Marshmallow, then tried updating to N again? Particularly after installing the April update?
Click to expand...
Click to collapse
How should I do this? I was reading this topic https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
and they said that necessary download russian firmware, is it right?
kaue152 said:
How should I do this? I was reading this topic https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
and they said that necessary download russian firmware, is it right?
Click to expand...
Click to collapse
I'm not sure. I believe you need a blankflash file for that firmware from what I've gathered, if it was a downgrade to Marshmallow after the April update for N, then updating back to N.
IncendiaryPyro said:
I'm not sure. I believe you need a blankflash file for that firmware from what I've gathered, if it was a downgrade to Marshmallow after the April update for N, then updating back to N.
Click to expand...
Click to collapse
I'm was updating for Nougat, probabily was that April update. Honestly I don't know what to do
kaue152 said:
I'm was updating for Nougat, probabily was that April update. Honestly I don't know what to do
Click to expand...
Click to collapse
Have you ever downgraded to Marshmallow at any time before that happened?
IncendiaryPyro said:
Have you ever downgraded to Marshmallow at any time before that happened?
Click to expand...
Click to collapse
Yep, I'm was using ViperOS, I'm downgraded to stock Marshmallow and was doing the OTA updates. When the phone reboot to install Nougat this happened.
kaue152 said:
Yep, I'm was using ViperOS, I'm downgraded to stock Marshmallow and was doing the OTA updates. When the phone reboot to install Nougat this happened.
Click to expand...
Click to collapse
Ah, so it was the update to Nougat that caused it. Yeah that has something to do with a bootloader upgrader in the April update I believe. You'll have to wait for a blankflash file to surface to repair that issue, unfortunately. Only reason I was asking was because I downgraded to Marshmallow a few months ago, then OTA'd back to Nougat, then also got the March update later down the road and never had any issues. I haven't gotten the April update yet but it'll be a good reminder to me not to downgrade to Marshmallow again.
IncendiaryPyro said:
Ah, so it was the update to Nougat that caused it. Yeah that has something to do with a bootloader upgrader in the April update I believe. You'll have to wait for a blankflash file to surface to repair that issue, unfortunately. Only reason I was asking was because I downgraded to Marshmallow a few months ago, then OTA'd back to Nougat, then also got the March update later down the road and never had any issues. I haven't gotten the April update yet but it'll be a good reminder to me not to downgrade to Marshmallow again.
Click to expand...
Click to collapse
How did you fix it? I found a blankflash and another rom to install
kaue152 said:
How did you fix it? I found a blankflash and another rom to install
Click to expand...
Click to collapse
I never had to fix it. I downgraded from the January patch for N (which I had sideloaded), OTA'd from Marshmallow to N + the February patch from my carrier, then I got prompted for March's update a few weeks later, so I guess there was never an issue downgrading back then, but something changed in April's patch that causes hardbricks when you downgrade and try to go back to Nougat. I've never had the April patch installed before so it hasn't affected me. From what I've read, it's only happened to people who had downgraded after installing April's update. Sorry I can't offer any help there. :/
PLEASE ALL GO TO THIS LINK
Http://lenovo-forums.ru/topic/20594-moto-z-play-obschaya-tema-voprosov-i-otvetov/#comment-550611
WHILE MORE OF US SEE AND LEN LIKE THE COMMENT OF
* VVizard @
SAGE
THEY COULD HELP US CHECK IT
Hello there. So, after flashing the TWRP my moto z play got bricked and now it remains at the "bad key" screen at boot. I can get into the fastboot screen and the recovery. To my understanding, I need to flash some firmware. My doubts are; does it matter which one of all I flash? And, most are marshmallow: I had nougat before this happened so, will I have trouble flashing these? Thanks!
Kon22 said:
Hello there. So, after flashing the TWRP my moto z play got bricked and now it remains at the "bad key" screen at boot. I can get into the fastboot screen and the recovery. To my understanding, I need to flash some firmware. My doubts are; does it matter which one of all I flash? And, most are marshmallow: I had nougat before this happened so, will I have trouble flashing these? Thanks!
Click to expand...
Click to collapse
Flash only system, data and boot. Do not mess with the modem, efs and bootloader images.
[GUIDE] Unbrick MOTO Z Play.... work in progress! (not working yet)
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Moto z play updated blankflash
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19
Go here .. flash the files and thank god and the OP.
I am using a rooted Z Play XT1635-02 and would like to un-root the device and restore it to stock. Can someone recommend a thread for me to follow. Thanks
[email protected] said:
I am using a rooted Z Play XT1635-02 and would like to un-root the device and restore it to stock. Can someone recommend a thread for me to follow. Thanks
Click to expand...
Click to collapse
download ROM from here[1] ( select appropriate country/region )
[1] https://mirrors.lolinet.com/firmware/moto/addison/official/
for flashing instructions ..go here [2]
[2] https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
jatinkhatri said:
download ROM from here[1] ( select appropriate country/region )
[1] https://mirrors.lolinet.com/firmware/moto/addison/official/
for flashing instructions ..go here [2]
[2] https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
Is this finally the SIGNED stock firmware? I've been dying to have it since I know the unsigned won't allow you to relock the bootloader.
Euroter said:
Is this finally the SIGNED stock firmware? I've been dying to have it since I know the unsigned won't allow you to relock the bootloader.
Click to expand...
Click to collapse
You'll never relock your bootloader , it's over and I can't understand why people think it makes a difference, moto has given you the unlocking key by asking for that key you are unlocked and unlock forever.
Read the unlocking agreement page from moto. You signed off on it.
You'll never ever see signed firmware from moto anyways , they keep them in house, all you'll ever see is unsigned firmware packages.
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Euroter said:
Is this finally the SIGNED stock firmware? I've been dying to have it since I know the unsigned won't allow you to relock the bootloader.
Click to expand...
Click to collapse
Nope...
core720 said:
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Click to expand...
Click to collapse
Please help. I successfully unlock bootloader and twrp but my big mistake was i erase user data via fastboot. My phones memory is empty. I tried to adb push zip file and whenever i flash it via twrp error says unable to mount data. I want to return in stock can u help me flashing/unbricking my mzp? I have the Android N firmware from russia. Can u teach me a step by step guide how should i survive my phone pleaseeeeee... thanks in advance
Kap_Tutan said:
Please help. I successfully unlock bootloader and twrp but my big mistake was i erase user data via fastboot. My phones memory is empty. I tried to adb push zip file and whenever i flash it via twrp error says unable to mount data. I want to return in stock can u help me flashing/unbricking my mzp? I have the Android N firmware from russia. Can u teach me a step by step guide how should i survive my phone pleaseeeeee... thanks in advance
Click to expand...
Click to collapse
Download the stock ROM ...extract it and run following commands turn by turn from the extracted folder ( you must have ADB tools installed )
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 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 system system.img_sparsechunk.9
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps
jatinkhatri said:
Download the stock ROM ...extract it and run following commands turn by turn from the extracted folder ( you must have ADB tools installed )
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 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 system system.img_sparsechunk.9
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps
Click to expand...
Click to collapse
Hi sir one of my friend telling that i dont need to flash the bootloader.img because it will make my device brick. He means that downgrading bootloader will be a problem? Please confirm
Kap_Tutan said:
Hi sir one of my friend telling that i dont need to flash the bootloader.img because it will make my device brick. He means that downgrading bootloader will be a problem? Please confirm
Click to expand...
Click to collapse
Yeah ...that can happen if you are on newer bootloader
So Skip bootloader.img
Moto Z Play Bricked
I have Moto Z Play. My device is totally bricked. When i try to boot my device it wont boot. Even fastboot mode wont work. When I connect this device to laptop, in device manager it shows Qualcomm HS-USB QDLoader 9008 & Notification LED Beside front Camera Constantly Starts Blinking. I had tried all the methods shown on XDA but i didnt find any solution from it.
If any one of a member from XDA knows this solution then please tell me.
Contact no- +91 9970631435
email- [email protected]
name- Mohammadzain Thakur
I want LOS14.1 on my phone, but it's better to keep on stock 7.1.1? Normally you are right, because it's stupid to change the rom just because the number (7.1.1 to 7.1.2).
Here you go, Android 7.1.1 Stock ROM for Moto Z Play.
https://www.androidfilehost.com/?fid=673368273298986785
Official ??
ROM_HUNTER said:
https://www.androidfilehost.com/?fid=673368273298986785
Click to expand...
Click to collapse
Is it official or wot ??
LovinVEVO said:
Is it official or wot ??
Click to expand...
Click to collapse
It's stock rom but not signed by Motorola.
ROM_HUNTER said:
It's stock rom but not signed by Motorola.
Click to expand...
Click to collapse
How can I update? Using RSD normally like another Stock ROM?
Fabio Magalhaes said:
How can I update? Using RSD normally like another Stock ROM?
Click to expand...
Click to collapse
Yes, or save this as a batch file and execute it.
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 NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Is it safe to flash gpt.bin? With other images there was a risk of hard-bricking if something went wrong there.
I only want to update my bootloader and firmware, so for that I'd do:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Question is if I should exclude the gpt.
Also: Is this compatible with reteu, or for what variant is it? I have XT1635-02 reteu.
BtbN said:
Is it safe to flash gpt.bin? With other images there was a risk of hard-bricking if something went wrong there.
I only want to update my bootloader and firmware, so for that I'd do:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Question is if I should exclude the gpt.
Also: Is this compatible with reteu, or for what variant is it? I have XT1635-02 reteu.
Click to expand...
Click to collapse
Just a headsup, updating only the GPT, bootloader and parts of the firmware is risky - unless you're already on the same patch level of the firmware. This is likely because only a partial flash may result in a mismatch between your system and your bootloader in terms of patch level. I don't recall the GPT causing hard bricks, it's more the bootloader that's a big cause of bricks because of having the aforementioned mismatch.
Thus, if you accept OTA updates, the OTA update will attempt to patch your device thinking that your system and bootloader are on the same patch level. As you've only done a partial update, the OTA will either fail or successfully patch, only to corrupt your mismatched bootloader, leading to a hard brick. We've seen this behaviour with downgrading a device's system (but not bootloader), so it'd be a similar state to your device if you updated like this and then accepted an OTA, and this bricking behaviour has been observed on partially updated Moto G4/Plus, Z Play and X devices, to name a few. Of course, you may receive an OTA update that may bring you to the same patch level as your updated bootloader/GPT, which may work, but it's a gamble.
Thus, if you're gonna update, fully update to the same patch level (that includes modem as well), do not mix and match parts of different builds (or if you do, remember not to update via OTA).
As for whether this build is suitable for EU devices, hopefully those who uploaded the stock ROM can comment.
echo92 said:
Thus, if you're gonna update, fully update to the same patch level (that includes modem as well), do not mix and match parts of different builds (or if you do, remember not to update via OTA).
Click to expand...
Click to collapse
I'm running LineageOS and am only looking for a way to update my bootloader and modem firmware.
What confuses me about this: It says NPNS, instead of just NPN or MPN. What's the meaning of those abbreviations?
The listed baseband version ends in an R. The one of other people ends with an e. It this just a typo?
BtbN said:
I'm running LineageOS and am only looking for a way to update my bootloader and modem firmware.
Click to expand...
Click to collapse
Hmm, I don't know if it'll work - in theory, it could as Lineage OS only affects your system/data. Of course, you'd have to remember that if you were to revert back to stock, to reflash at least the same stock ROM as your bootloader patch level.
Still would be better to completely flash the same stock ROM onto your device (of course this would wipe Lineage and TWRP off your device). What do you hope to gain from updating your bootloader/GPT and modem compared to your existing firmware?
As far as I know:
MPN - Marshmallow firmware
NPN - Nougat firmware
NPNS - Nougat firmware with added security patch updates
Usually your baseband, from what I've seen, ends in R (e.g. for Moto G4, our latest basebands end in 62.01R). If it ends in e, it's either a typo or something has gone wrong with the underlying firmware, I've not noted working modem firmware working if ending in anything other than R.
echo92 said:
Usually your baseband, from what I've seen, ends in R (e.g. for Moto G4, our latest basebands end in 62.01R). If it ends in e, it's either a typo or something has gone wrong with the underlying firmware, I've not noted working modem firmware working if ending in anything other than R.
Click to expand...
Click to collapse
My current baseband ends in an e, according to the Phone Status page in my settings. See attached image.
Just want to be up to date with what LaOS expects. As it declares 7.1.1 to be the target, and my device has not gotten any firmware updates since the first 7.0 firmware which it updated to when I got it.
On another note, putting the filename into google ends up with this link: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Looks pretty official to me. The sha1sum of that file is e94b9690de5417b4499d8995726ccaf5d0492d5e
So whats are the correct steps?
Should I flash gtp or not?
---------- Post added at 08:52 PM ---------- Previous post was at 08:52 PM ----------
So whats are the correct steps?
Should I flash gtp or not?
Hi, hyoga68. I´ve updated my Moto Z Play using RSD, but you can do by prompt. I think you´ll be in trouble if you downgrade ROM, but in this case we´ll be updating, with the newest ROM avaible.
Fabio Magalhaes said:
Hi, hyoga68. I´ve updated my Moto Z Play using RSD, but you can do by prompt. I think you´ll be in trouble if you downgrade ROM, but in this case we´ll be updating, with the newest ROM avaible.
Click to expand...
Click to collapse
Thanks, will try to get a PC with Windows, and try with RSD ...
Did anyone try to re-lock the bootloader with this image?
Thanks!
New Stock ROM with September Security Patch: upped by Rickk182440 - https://androidfilehost.com/?fid=889964283620757667
Fabio Magalhaes said:
New Stock ROM with September Security Patch: upped by Rickk182440 - https://androidfilehost.com/?fid=889964283620757667
Click to expand...
Click to collapse
Can I clean flash this over a custom ROM on my reteu MZP?
MZP with unlocked bootloader?
Fabio Magalhaes said:
MZP with unlocked bootloader?
Click to expand...
Click to collapse
Hint: Custom ROM is not possible without.
Deleted
tag68 said:
Hint: Custom ROM is not possible without.
Click to expand...
Click to collapse
So... Go on
How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)
I am currently on lineage OS 14.1 (7.1.2) dated 18.09.2017.
I want to go back to stock firmware as I am facing some issues with lineage.
How to find the latest firmware. Found this website which has all the images https://firmware.center/firmware/Motorola/Moto Z Play/Stock/XT1635-02/
But I am unable to select the correct one for my device. (do not want to brick it). Also found another thread stating latest firmware
https://forum.xda-developers.com/moto-z-play/help/addisonnpns26-118-22-1cid50subsidy-t3675521
I am an Indian MOTO Z Play
Is there a way to go full stock and also start to receive OTA updates. Can someone provide me with full guide with links?
First you need exactly your software channel and the build of your baseband and bootloader. You know how to get this information?
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
kkube said:
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
Click to expand...
Click to collapse
I'll be waiting for it.
Process to go from custom rom back to stock (August update)
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
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 NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Click to expand...
Click to collapse
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
And can we do OTA updates after doing this?
Thank you so much for this guide, my phone was rebooting to recovery every single time and nothing worked. I flashed this rom as you said and my phone just booted and it's working. I can't believe it.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
Click to expand...
Click to collapse
My phone is reteu and after flashing is still on reteu, so it should be fine, dont worry. Also you should get any future updates via OTA.
kkube said:
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Click to expand...
Click to collapse
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
akshaypatil869 said:
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Click to expand...
Click to collapse
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
Does anyone receive the update with September patch via OTA after back to stock following post #5 instructions?
This a fantastic guide - THANKS!!! - I have linked to it giving credit. Thanks!
I have also a thread, if you follow that one. Bootloader is locked/ u will be able to get ota'$
Hello, I'm a Motorola Moto G5 owner and I rooted my device some time ago.
Now i found out there is an official motorola update which brings our moto g5 from nougat to oreo. I'd want to update my phone but I have the little problem I cannot update my phone using the regular "System Updates" section in settings because I have a custom recovery and every time I try to update the phone just boots in twrp and to use it I must restart in bootloader and then press on start.
I've found online some official ota updates zips so my question is: Can I just install these zips with the install zip twrp function instead of reflashing stock firmware just to install a few updates? Is there another more simple way to update this damn phone? (I have Magisk 1.19, I'm on build NPPS25.137-93-8 and I'd want to get to the latest one)
(Oh yeh, srry for bad english but it isn't my mother language)
OnionMaster03 said:
Hello, I'm a Motorola Moto G5 owner and I rooted my device some time ago.
Now i found out there is an official motorola update which brings our moto g5 from nougat to oreo. I'd want to update my phone but I have the little problem I cannot update my phone using the regular "System Updates" section in settings because I have a custom recovery and every time I try to update the phone just boots in twrp and to use it I must restart in bootloader and then press on start.
I've found online some official ota updates zips so my question is: Can I just install these zips with the install zip twrp function instead of reflashing stock firmware just to install a few updates? Is there another more simple way to update this damn phone? (I have Magisk 1.19, I'm on build NPPS25.137-93-8 and I'd want to get to the latest one)
(Oh yeh, srry for bad english but it isn't my mother language)
Click to expand...
Click to collapse
No you cannot
Firmware OTA zips can only be installed on a totally unmodified stock system image
You will need to flash the stock firmware via fastboot and I recommend to lock the bootloader to ensure that the firmware is totally unmodified before doing any ota updates else you risk hard bricking the device
Firmware can be found
https://mirrors.lolinet.com/firmware/moto/cedric/official/
TheFixItMan said:
No you cannot
Firmware OTA zips can only be installed on a totally unmodified stock system image
You will need to flash the stock firmware via fastboot and I recommend to lock the bootloader to ensure that the firmware is totally unmodified before doing any ota updates else you risk hard bricking the device
Firmware can be found
Click to expand...
Click to collapse
Ok well, how to lock bootloader (Right now I have unlocked bootloader)? How to reunlock it after (Do I just need the same guide to unlock as the first time?)? But most important, how to install the stock image by fastboot? (What's the exact command?)
Oh well, I just noticed the firmwares you sent me are already on Oreo 8.1.0, Could I just install one of them and then reroot the phone?
OnionMaster03 said:
Ok well, how to lock bootloader (Right now I have unlocked bootloader)? How to reunlock it after (Do I just need the same guide to unlock as the first time?)? But most important, how to install the stock image by fastboot? (What's the exact command?)
Click to expand...
Click to collapse
Use the Oreo TWRP flashable zip for Moto G5 https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913.
Andrej_SK said:
Use the Oreo TWRP flashable zip for Moto G5 https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913.
Click to expand...
Click to collapse
Really thank you!
OnionMaster03 said:
Ok well, how to lock bootloader (Right now I have unlocked bootloader)? How to reunlock it after (Do I just need the same guide to unlock as the first time?)? But most important, how to install the stock image by fastboot? (What's the exact command?)
Oh well, I just noticed the firmwares you sent me are already on Oreo 8.1.0, Could I just install one of them and then reroot the phone?
Click to expand...
Click to collapse
Yes you can flash the latest firmware for your device and root with magisk
Google is always your friend for how tos
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
You can stop here if you intend to root etc or carry on if you want to relock the bootloader
Relock bootloader (note if you do this you won't be able to flash twrp or root etc)
Code:
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 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 boot boot.img
fastboot oem lock
Device will restart
Now flash the entire firmware again (first list)
Note unless you have all the unlock keys you may not be able to unlock it again