ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip - Moto Z Play Questions & Answers

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

Related

I bricked my z play

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.

XT1710-08 changing Stock ROM

i wanted to know that is there any way to get rid of that ZUI interface in china retail model of the z2play? by flashing a stock international firmware? I'm planning to buy one from china but it's coming with lenovo's ZUI interface...
thanks
yes, u can do it
Khanov said:
yes, u can do it
Click to expand...
Click to collapse
And with what version of stock rom ??
Thanks..
Guth13 said:
And with what version of stock rom ??
Thanks..
Click to expand...
Click to collapse
I have read about retail one, on firmware center, but i am still waiting for my device from bangood.
Have a try, taking care about modem (it seems dosn't work if you don't preserve the original one).
HTCDevil said:
I have read about retail one, on firmware center, but i am still waiting for my device from bangood.
Have a try, taking care about modem (it seems dosn't work if you don't preserve the original one).
Click to expand...
Click to collapse
Hello. I own the Moto Z2 Play Mod: XT1710-08 with the ZUI. I would like to take it the stock ROM, but I don't know which model can be fine with my device.
Has anyone already tried or can it help me?
Thanks so much
Simone
bysimo95 said:
Hello. I own the Moto Z2 Play Mod: XT1710-08 with the ZUI. I would like to take it the stock ROM, but I don't know which model can be fine with my device.
Has anyone already tried or can it help me?
Thanks so much
Simone
Click to expand...
Click to collapse
i changed Rom to stock Blur Version ROM NPSS26.116-19-1-6.
During flash steps, i didn't flash adspso.bin, non-hlos.bin, modem.bin and fsg.mbn.
My phone is working with IMEI fine.
Thank you, but after several days i have posted here my solution: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153/page1
zuiudo said:
i changed Rom to stock Blur Version ROM NPSS26.116-19-1-6.
During flash steps, i didn't flash adspso.bin, non-hlos.bin, modem.bin and fsg.mbn.
My phone is working with IMEI fine.
Click to expand...
Click to collapse
Hi, Do u have a link?
Also if you're just concerned with the launcher (it's terrible!) you can just install another launcher from the play store.
zuiudo said:
i changed Rom to stock Blur Version ROM NPSS26.116-19-1-6.
During flash steps, i didn't flash adspso.bin, non-hlos.bin, modem.bin and fsg.mbn.
My phone is working with IMEI fine.
Click to expand...
Click to collapse
Does your fingerprint sensor still work?
Another method
pjcons said:
Does your fingerprint sensor still work?
Click to expand...
Click to collapse
I am not an expert in this area, but just wanted to share a method that worked for me to convert ROM of XT1710-08 China variant phone (with Android 7.1.1 ZUI interface) to Oreo 8.0.0 US retail version
Basically I followed the instructions from below thread with some changes.
https://forum.xda-developers.com/z2-play/how-to/how-to-manually-update-moto-z2p-to-t3677357
I had already unlocked bootloader and not sure if that was really needed for this. (Make sure you have USB drivers and latest adb/fastboot utilities and verify fastboot is working with the phone)
1. Using fastboot, flashed the 8.0.0 Chinese ROM from https://mirrors.lolinet.com/firmware/moto/albus_retcn/official/RETCN/
Please note, system.img and oem.img may be split into multiple files, so update the .bat file accordingly.
2. next, flashed the US retail version from https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Here I skipped the modem related images (NON-HLOS.bin ,fsg.mbn , dsp adspso.bin , and did not erase modemst1 and modemst2) - see below commands from the bat file.
echo off
echo -------------------------------------------------------------------------
echo Moto Z2 Play ROM Flash Start
echo -------------------------------------------------------------------------
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
echo skip fastboot flash modem NON-HLOS.bin
echo skip fastboot flash fsg fsg.mbn
echo skip fastboot erase modemst1
echo skip fastboot erase modemst2
echo skip 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 oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo Moto Z2 Play ROM Flash End
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
3. Reboot to recovery and do factory reset. This is important. For me the the phone went into a boot loop, until I did this reset.

MOTO G5 PLUS fastboot stock Oreo 8.1.0 Rom

Here it is most awaiting fastboot rom file...
https://drive.google.com/folderview?id=1NR--EZXzMCzbKT0GCBp3gKbp5TrU_ImE
POTTER_RETAIL_8.1.0_OPS28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
fastboot commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
if you ever played with your persist, its not fixing those persist who flashed other device persist to gain IMEI and VoLTE, safe for those who never played with their persist and for those who are having baseband with ending with capital R. Direct flashing via fastboot ending with no signals and also not imei if dont skip erase modemst1
erase modemst2.
Guide for those who are not on their own persist but with another persist able to use Signals with volte and using any custom or nougat or twrp rom
first take backup of your current working efs and persist on sd card or otg
Thn flash above rom via fastboot, dont skip anything, reboot system thn again go in fastboot menu
Flash twrp, thn in twrp only flash only FIRMWARE from SOAK Test 1 Aroma by @NZedPred ( https://www.androidfilehost.com/?fid=1322778262903990826 ), Thanks @NZedPred for his great work, now restore your efs and persist, roboot system.
If you want to lock bootloader thn follow these commands in fastboot
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
All of these worked for me as I was also not on my own persist.
everything working fine CAMERA, VOLTE, WIFI, FINGERPRINT, locked bootloader and unlocked also again with my key tht provided by moto, battery also charging faster, battery backup is also good.
Hey, will this work for hard bricked users? I've been using twrp flashable nougat stock ROMs since last year! Can't get back to full stock so!
irfanalinawaz said:
Here it is most awaiting fastboot rom file...
https://drive.google.com/folderview?id=1NR--EZXzMCzbKT0GCBp3gKbp5TrU_ImE
POTTER_RETAIL_8.1.0_OPS28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
fastboot commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
skip
fastboot erase modemst1
fastboot erase modemst2
if you ever played with your persist, its not fixing those persist who flashed other device persist to gain IMEI and VoLTE, safe for those who never played with there persist and for those who are having baseband with ending with capital R.
For those who played with their persist, there are IMEI but no network after restoring EFS and Persist backup with TWRP, so be careful.
Click to expand...
Click to collapse
With ota instalation my radio say is off....with the fastboot And jumping erase modems... Rádio Will work?
Same quesrion but nomore but to try anyways
LLegion said:
Same quesrion but nomore but to try anyways
Click to expand...
Click to collapse
Radio will work if your Persist is intact, and you never flashed others persist to gain imei and volte otherwise there are no signal. I have tried all the methods but stll working on it, let see...hope.
irfanalinawaz said:
Radio will work if your Persist is intact, and you never flashed others persist to gain imei and volte otherwise there are no signal. I have tried all the methods but stll working on it, let see...hope.
Click to expand...
Click to collapse
Tried put Oreo with one sim card only?
Another devices doing this work to get radio ?
david.gs.gm said:
Tried put Oreo with one sim card only?
Another devices doing this work to get radio ?
Click to expand...
Click to collapse
I have tried something different I was able to gain network with volte but signals are not stable they coming and going, anyways it will take time, nothing is impossible here, I am also one from those who messed up thier Persist, and I am working on it.
irfanalinawaz said:
Radio will work if your Persist is intact, and you never flashed others persist to gain imei and volte otherwise there are no signal. I have tried all the methods but stll working on it, let see...hope.
Click to expand...
Click to collapse
help me out with an issue about retail or my software channel is retin should this version is good for me to install my build number is NPNS25.137-92-14 and I already got OTA update but my persists is not mine what should I do
This means TWRP flashable is on its way.:good:
devvshukla said:
I got some errors while sending these two commands, device is working regardless of these errors.
Which are these command and whats they do? Also what issues I might be facing on future because of this?
Commands -
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
These commands are not nessecery, ignore them and proceed. These commands will not affect any future ota or update.
livyansh said:
help me out with an issue about retail or my software channel is retin should this version is good for me to install my build number is NPNS25.137-92-14 and I already got OTA update but my persists is not mine what should I do
Click to expand...
Click to collapse
Bro you need to avoid this to flash, right now there is not any solution for those who are not on their persist, you will end up with no signals. So wait, I am still working on it.
rajeshkoshti said:
This means TWRP flashable is on its way.:good:
Click to expand...
Click to collapse
We already have that from beta. The latest beta was same as official release.
livyansh said:
help me out with an issue about retail or my software channel is retin should this version is good for me to install my build number is NPNS25.137-92-14 and I already got OTA update but my persists is not mine what should I do
Click to expand...
Click to collapse
After upgrading to oreo, download the Oreo flashable zip (Aroma) of SOAK1 and install only the firmware. And restore your efs after this step.
My phone is working perfectly with this, no network issues.
irfanalinawaz said:
Bro you need to avoid this to flash, right now there is not any solution for those who are not on their persist, you will end up with no signals. So wait, I am still working on it.
Click to expand...
Click to collapse
okay, bro, I am waiting just let me know whenever you find out any solution about VOLTE or no network issues
antojamez said:
After upgrading to oreo, download the Oreo flashable zip (Aroma) of SOAK1 and install only the firmware. And restore your efs after this step.
My phone is working perfectly with this, no network issues.
Click to expand...
Click to collapse
There are also many hidden issues after this method, wifi is getting slow while Bluetooth is active, if Bluetooth inactive thn also there are frequent wifi disconnection. Fingerprint also getting so slow while screen is off, I already tested it.
devvshukla said:
I got some errors while sending these two commands, device is working regardless of these errors.
Which are these command and whats they do? Also what issues I might be facing on future because of this?
Commands -
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
Hey I also got that errors after few time my device got hard bricked.
riyan65 said:
Hey I also got that errors after few time my device got hard bricked.
Click to expand...
Click to collapse
These commands are not responsible for hard bricks, may be there are another reason for hard bricks.
Asking again...
Will this work for hard bricked users? I've been using twrp flashable nougat stock ROMs since last year! Can't get back to full stock so!
roydhritiman said:
Asking again...
Will this work for hard bricked users? I've been using twrp flashable nougat stock ROMs since last year! Can't get back to full stock so!
Click to expand...
Click to collapse
First post your fastboot getvar here, then tell me what is the condition of your persist, imei, volte etc. Also from fatboot menu take a pic and post them also, and describe how you recovered your hard bricked device, then we can explain you. Thanks.
irfanalinawaz said:
Bro you need to avoid this to flash, right now there is not any solution for those who are not on their persist, you will end up with no signals. So wait, I am still working on it.
Click to expand...
Click to collapse
but I got the OTA update on my phone to download and I did that but I am the little bit afraid to install it just because of VOLTE and IMEI

Moto G5 install ota by zip on rooted phone (Can I just install ota zips with twrp?)

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

Downgrade Z2 play pie to oreo

Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?
Anything below Pie is vulnerable to the X-helper rootkit... we were just talking about it in another thread. It's a real nasty little bugger.
But its posible? I just want to get all the features back, even, i dont know what is that thing, if they have some to hack me i dont have to much to lose anyways, just want to downgrate to fix the fingerprint bug from oreo
Don't know. Hopefully someone with this device can help you.
iMaxwell said:
Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?
Click to expand...
Click to collapse
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running
marcost22 said:
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running
Click to expand...
Click to collapse
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat
iMaxwell said:
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat
Click to expand...
Click to collapse
that's probably the worst available way to do it. If your phone didn't originally receive it via OTA, then you are forcing it the wrong way.
If you want to go back to nougat all you need to do is download the official N firmware, then flash everything but bootloader and gpt
What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that
I follow the steps on this video
iMaxwell said:
I follow the steps on this video
Click to expand...
Click to collapse
Yeah that is just terrible
iMaxwell said:
What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that
Click to expand...
Click to collapse
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash 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 oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice
marcost22 said:
Yeah that is just terrible
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash 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 oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice
Click to expand...
Click to collapse
The issues begin on official oreo, i upgrade nougat to oreo then, fingerprint option dissapear, then i upgrade to pie from oficial firmware but issues still remain
It really works? I didnt find any video or post about downgrade like that
Yes it does work, but it's not recommended, that's why you don't find much info
iMaxwell said:
It really works? I didnt find any video or post about downgrade like that
Click to expand...
Click to collapse

Categories

Resources