yashsingh1/xdaforums huggingface dataset:
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] jonas210678:
It is not needed to have an unlocked bootloader to flash fastboot images. You can flash them with an locked bootloader too

---------- Post added at 05:44 PM ---------- Previous post was at 05:29 PM ----------

Here are so much question if this fastboot images can be flashed on this rom or that device.

This fastboot firmware can be flashed on every xt1635-02. No matter what rom you use, you can be on 6.0.1 or on soak test, 7.1.1 or oreo every software channel, unlocked or locked bootloader, or on an any custom rom.

When you use ops commands it will wipe everything out of the device and is like a new stock Moto phone.

The only thing you can't do is, flashing the fastboot firmware on an phone with newer firmware, but this is at the moment not possible because there is no firmware with may security patch.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Tepig:
I didn't know this, thanks for the info!
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] djdelarosa25:
But there is already a guide on how to flash the Oreo firmware and relock the bootloader.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Brann_97:
I already checked it, but they are only compatible with Nougat, I have the brick in Oreo. But I still appreciate it! :)
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Kennedy.Barreto:
I tried root with magisk v16 but it stays in loop ... is there any way to get root in oreo 8.0 stock?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] antoss:
haow about xt1635-03 device?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] speedepl:
I sideloaded oreo to my MZP, but used wrong cable. Now I have security error message at boot.

Will this method fix the error message?

Today I have used fastboot without the line "fastboot erase userdata". The error message is fixed, all my data untouched.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] duarttmarcelo@gmail.com:
My xt 1635 has a link with the local "VIVO" operator, with software channel "tefbr"

How do I change to "RetBR"?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] djdelarosa25:
I was already running official Oreo on my Moto Z Play (Build number OPN27.76-12-22) that I flashed using this guide when the OTA update arrived for retapac devices. As my device was retapac, and also due to OCD, I decided to download the update zip from this website (motooata.lolinet.com) and sideload the same update again (I know, it's stupid, but please bear with me). Everything went smoothly, but now battery life has gotten worse. I plan on flashing the fastboot file again but I don't want to wipe my user data. What commands do I need to omit to achieve this?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] fystrified:
Have you tried clearing your device system cache in recovery mode?

---------- Post added at 08:38 AM ---------- Previous post was at 08:38 AM ----------

Have you tried clearing your device system cache in recovery mode?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] djdelarosa25:
I have. A user on Reddit told me to wait for a couple of days for the cache to settle. What do you think?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] jonas210678:
I would wait too. Maybe it is an app what is causing the battery problem. But when you really want to flash fastboot, don't use the wipe userdata command.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] djdelarosa25:
I tried using BetterBatteryStats to check and no app seems to be causing an undesirable amount of wakelocks. Btw, both SoT and idle battery drain are hit. I slept last night with about 20+% left and woke up to a phone with no charge.

Also, before I sideloaded, I didn't have the battery drain issue. The apps that I had then I still have now. I'm guessing it's really the Android system's fault.

I'll give it a week and report back to you if anything changes. If not, I'll do a factory reset.

Thanks for helping!
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] fystrified:
Deleted
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] djdelarosa25:
Battery life has stabilized, thankfully.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Egasparotto:
What is de Encryption password?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] pgravier@ebuyclub.com:
XT1635-03

I have the same question ? Can I apply to XT1635-03 (currently on 7.1..1 NPNS26.118-22-2-3 security patch October 1st)
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] mijing:
Can I flash this? I was using custom ROM since update up to android 7.0. Can I flash this stock oreo image with fastboot without problems?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] rafikowy:
Of course you can. :)
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] mijing:
Thanks for quick replayed anyway I will update tomorrow
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] luks_p:
Can I deny the command above to prevent bootloader update?

I'm on NPNS26.118-22-2-17 (Feb 1, 2018 security patch).
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] echo92:
In theory you could, but you'd need an unlocked bootloader to do so (else you may soft brick your device). Subsequent OTA updates would update your bootloader anyways.

I'd normally advocate keeping your bootloader and your system on the same patch level, what do you hope to do with a Feb 2018 bootloader?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] WiserJr:
Me too
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] luks_p:
Thank you.. I just thought about going back to Nougat.

Finally, I upgrade to this Oreo following the instructions on 1st post. But I'm facing heavy battery drain compare to stock Nougat.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] echo92:
Hmm, did you factory reset your device with the 'fastboot erase userdata' and reset your cache with 'fastboot erase cache'? If so, you may be experiencing battery drain as your device sets itself back up after a major OS upgrade.

If you really want to revert back to stock Nougat, the only real safe firmware would be the Feb 2018 7.1.1 firmware, as that's the firmware directly preceding the Oreo firmware (as of writing this), so the OTA update you'd receive would be the update to stock Oreo, which is the current latest firmware. Downgrading to any older Nougat firmware may give you an older OTA update which may hard brick your device. By extension, once Oreo OTA updates begin, it's no longer safe to downgrade to Nougat unless you do not use OTA updates. At the moment, hard bricks involving devices updated to Oreo are not rescue-able without an expensive motherboard replacement.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] user822:
Hey folks, is the instruction what to flash by Alberto still valid, when just upgrading the firmware parts?

https://xdaforums.com/moto-z-play/d...ageos-15-0-t3682736/post74069195#post74069195

Thank you

Edit: worked for my reteu on Alberto's AOSP rom, but no gurantees that this does not do anything bad to your phone
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] luks_p:
Yes, I followed all the instructions on 1st post.

So, is it save to revert back to the latest stock Nougat by deny OTA update?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] echo92:
I can't say if it's safe, I don't think you'll have issues reverting back to the latest stock Nougat if your bootloader is unlocked. However, you may see 'security downgrade errors' when flashing the GPT/bootloader, as you cannot downgrade bootloaders usually - you can ignore these errors when flashing. However, because you cannot downgrade bootloaders via fastboot, it becomes risky when taking OTA updates, as OTA updates can flash a bootloader without verification, which means if your device is downgraded too far (more than one preceding firmware), you may hard brick. At the moment, I don't see any issues downgrading to the Nougat 7.1.1 Feb 2018 firmware, but if you want to update, safest to flash the full Oreo firmware.

Also, as you need an unlocked bootloader to downgrade, you'll have the downsides of an unlocked bootloader to deal with - namely Safetynet tripping and loss of Android Pay, plus inability to use some apps. You could root and use magisk to hide your bootloader unlocked status and try to get SafetyNet back. If you ever wanted to re-lock your bootloader, you'd have to flash the latest Oreo firmware, Nougat firmware will not re-lock your bootloader if you formally updated to the C182 Oreo bootloader.

You may also be repeatedly informed of OTA updates, in which case you'll need to root and disable the Motorola updater.

However, you may wish to wait a couple of days after the clean flash to see if your device settles down. I recall apps like Google Photos will drain your battery heavily as it's syncing, especially if you have a lot of photos. If you want to, you can check if any apps are draining battery with Better Battery Stats or GSAM Battery Monitor.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Brann_97:
Could someone share an image of the fastboot mode menu on their smartphone after upgrading to Oreo?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] WiserJr:
Is the same as the 7.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Brann_97:
Do you know if there is any way to know if the z play had already been updated to 8.0?

I bought a used one, but I do not know if they installed soak test or something like that, I want to avoid the hard brick again
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] echo92:
If I recall correctly, if you see C180 or C182 as your bootloader version, then at some point your device was updated to Oreo (if you're running the retail build that's flashable from various pages here or were on the Oreo soak tests). I don't know if this also holds for other variants or releases of Oreo to carriers or other regions. C1:14 is the bootloader from the Nougat 7.1.1 retail Feb 2018 security patch firmware, and I think the C1:13 bootloader was the December 2017 security patch 7.1.1 retail firmware. As you usually cannot downgrade bootloaders, it's a decent first step to identifying if your device was updated to Oreo.

If you really want to check, you can pull the getvar data:

Connect your device to your computer. Boot your device to the bootloader.

Open up ADB on your computer. Check your device is communicating by entering 'fastboot devices' without quotes. Pressing enter on your keyboard should return your device serial number.

If you get a response, then type 'fastboot getvar all' without quotes. Press enter. That should return an output of your device parameters.

Things to look for: is the warranty void parameter reporting as yes? If so, then the bootloader was unlocked previously.

Is the device in oem_locked or flashing_unlocked status? If Oem_locked, then it's unlikely you can hardbrick as a locked bootloader only lets you flash the same or newer firmware. If flashing_unlocked, then be careful with OTA updates; it's not the downgrading of your stock firmware that bricks your device, it's using old OTA updates on a downgraded device that hard bricks.

If you want to, you can post the output here from the getvar all, just please remove your IMEI from the post.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] luks_p:
I'm sorry I forgot to say that my bootloader is unlocked.

So, bootloader won't be upgraded/downgraded automatically if we deny OTA?

I don't use (and don't care about) android pay.

My battery drain is terrible or maybe weird. Screen on or off, even in flight mode, the battery is constantly drained (screenshot attached).
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] JonasVFC:
me too. were you able to solve the issue?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] JonasVFC:
did someone manage to root this? i'm getting boot loop after flashing magisk and f2fs workaround bug
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] WiserJr:
I got. Uninstall magisk and install again. Reboot and will work.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] JonasVFC:
What versions did you flash?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] WiserJr:
magisk 16

---------- Post added at 11:06 PM ---------- Previous post was at 11:02 PM ----------

Follow this guide: https://xdaforums.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273

Update 20/04/2018
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] JonasVFC:
That was exactly what I did. But it gets stuck at "your device is unlocked and cannot be trusted " screen. I even flashed uninstalled and installed again like said on that thread. How much time did it took you to boot after flashing?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] WiserJr:
Seconds...
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] luks_p:
My battery back to normal after last reboot. I don't really know what happened or what is wrong before.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] echo92:
Good to hear your battery is back to normal.

It's possible that some apps were doing a lot of downloading and synchronising after the clean flash, and now that's done, your device is settled down. For example, after flashing a custom ROM, I'd note that Google Photos would keep my device warm and drain the battery until the synchronisation was completed - a similar thing would occur on a clean flash of the stock ROM as well. Or the reboot reset something...?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Brann_97:
Here it is, also I noticed that the IMEI does not appear in the cell phone options, it appears as "0", while in ADB it appeared normal.

I really do not want to modify any of the software, let alone damage another logic card :( That's why I want to proceed with great care.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] echo92:
Thanks for the image. A few things about that device:

1)It's got the C1.12 bootloader, so that suggests you do not have the Oreo update on that device. The build currently flashed onto it suggests it's the Sept 2017 security patch 7.1.1 firmware.

2)However, your baseband is ending in a (.65a), rather than R, which is what we normally see with working IMEI/SIMs. That, in tandem with the flashing_unlocked bootloader, suggests that the previous user may have flashed the incorrect stock ROM, and messed up the baseband.

3)That device software channel is attmx (AT&T Mexico), and I honestly do not know if you can flash retail firmware on such a device. I've read of instances where flashing retail firmware onto carrier linked devices can mess up the baseband too, and I don't also know if there is attmx firmware to restore the device. Also, I do not know if the device will work in your region unless you're also in Mexico.

You may be able to flash Oreo (but please do not downgrade to Nougat), or flash stock Nougat ROMs as new or newer than Sept 2017 (but if you do update, only flash firmware as new as your update). However, I think they may not fix your IMEI issues.

Unless you can find a straightforward fix, I would honestly return the device to the seller for a refund. IMEI issues are a pain to reliably fix.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Brann_97:
I really appreciate the advice, I'm from Mexico and honestly, the device I got at a very low price, the equivalent of $ 20 dollars, the only drawback was that the display was damaged, however I had my previous device in good condition, so I decided to put the screen I had on the device damaged by the hard brick. Currently works without problems, except for the IMEI, but when making calls and networks is all right.

I just wanted to find out how likely it was to suffer a hard brick, because I did not know if it had already been updated. Again, thank you very much for the help, a warm greeting from Mexico!
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] echo92:
Ah, thank you for the greetings :)

That sounds like a bargain, and at least your device is working. With hard bricks, the main reason I've seen when it comes to updates is having downgraded firmware. As it looks like you already have the Sept 2017 firmware on there, you may be okay. However, as soon as you start using OTA updates or flash a newer stock firmware, only flash stock firmware that is as new or newer than the latest firmware on your device to avoid hard bricks (e.g. if you update to the Feb 2018 7.1.1 firmware, please only flash Feb 2018 or newer stock firmware to your device. Same goes for Oreo, please avoid downgrading to Nougat after flashing Oreo). Alternatively, if you still want to flash older stock firmware, disable OTA updates, or use TWRP flashables of the stock ROM.

The reason for hard bricks with updates appears to come from the bootloader not being downgraded when you flash older firmware. For example, on Oreo you have the C182 bootloader. Flashing the Dec 2017 firmware onto that device would downgrade your system to Dec 2017, but you'd still have the Oreo bootloader. Fastboot would stop you from flashing the older bootloader to your device. Hence, you have a mismatched device firmware and bootloader. Your device may boot fine afterwards until you take an OTA update...

The OTA update does not appear to check your bootloader version (reading the OTA script, there seem to be no checks for bootloader version, despite there being checks for system, OEM and modem integrity amongst others). It seems that the OTA updater script assumes that your device firmware and bootloader are matching, which if you downgraded is not a correct assumption (and probably is why, in the Motorola OTA update notes, they advise you cannot downgrade). For the above example, you would be able to download and begin installing the Dec 2017 to Feb 2018 OTA update. However, the OTA would begin flashing the Feb 2018 Nougat bootloader onto an Oreo bootloader, and thus you'd hard brick.

Hence, if you want to avoid hard bricks, please only flash stock firmware as new or newer than the latest stock firmware that was on your device (make a note of the firmware version before you flash custom ROMs).
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Abhishek420:
I'm on Alberto's 8.1 custom rom.... will this work? And not brick my device
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] 18Aniruddha:
Need Blank Flash files for Moto Z Play

nee a blank flash file for moto z play
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Warkratos:
Can I do this without unlocking Bootloader? just to clean install all the OS?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] JonasVFC:
no.

if you want a clean install without unlocking the bootloader, do a factory reset.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] KrisM22:
I RSDlite'ed this (win7) and seems to be fine - security is at Apr - is that simply the latest one?

MANY THANKS!!!
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] KrisM22:
root w/o TWRP? - edit - solved.

I would like to try to take updates ota for a bit and putting TWRP on will kill that.

I grabbed the latest TWRP apk and installed it, and it tried to download and install 16.0, - downloads fine but error msg can't unpack it.

By the way PoGo works fine on this one, as yet unmodified. Would like root for fireflash or whatever it is.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] erick0023:
Its Now
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] KrisM22:
?what is that? an update to [MENTION=5750370]rafikowy[/MENTION] 's 8.0 signed?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] klofisch:
I lost dual sim support after update. Can u use the same procedure as for Nougat to get it?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] DávalosAlberto:
Dude

is there any way to update a Moto Z Play without a PC? the problem is that my Moto Z play does not recognize any pc despite having installed the drivers and nothing appears in the notification bar of the cell phone, and probe to activate the USB debugging and neither does it only charge the battery
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] masteguh:
i have a Moto z Play 1635-02 dual SIM with unlock bootloader, TWRP and no ROM. coz accidentally i format em on TWRP without back up. the question is can i use this method to bring it life once more ?

FYI : im on OPNS27.76 12-22-3
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] dado_13:
Yes, flash rom using adb, but flash only latest version OPNS27.76 12-22-3 , because if you flash older version, you will downgrade bootloader and you are risking hardbrick (if you ever accept OTA ). Latest version can be found somewhere in this forum (if you struggle to find it, pm a I'll look).
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] masteguh:
i found one in this thread but ... it always end fielded. so if you have a mirror will be gud.

and insted of ADB can i use this methode ?

https://www.youtube.com/watch?v=08RxXGUyVfI

coz i faceing some issue with ADB on win 10

https://imgur.com/O5YRaQX
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] alexche77:
Hi,

I was wondering which process to follow if we want to root and install TWRP again on this device with Android 8 after applying this files.

I am asking because I can see that with those commands we wipe our current recovery.

Thanks in advance.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] SLR96:
Hi... I have a dual sim mzp as well, I have a 7.1.1 rom installed from this thread:

https://xdaforums.com/moto-z-play/development/rom-single-dual-sim-t3620551

My device is an unlocked XT1635-03 on retcn channel

I was just wondering what happened to your phone? were you able to get both sims to work?

Also can I flash this rom using twrp? twrp is much easier and straight forward, and I'm kind of a noob and can't afford to risk anything
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] rafikowy:
Thread updated - FASTBOOT STOCK OREO IMAGE OPNS27.76-12-22-9 added (the newest available for now).
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] DomBuback:
Hi, dude.

ATTENTION:

Magisk does'n work on this image!

I have tried all versions but no success.

If anyone knows how to root this version, share with us.

Thanks!
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] KrisM22:
You might try some of the stuff we did on Pie.

Look at this post and go backwards.

https://xdaforums.com/showpost.php?p=77577440&postcount=275
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] DomBuback:
Hi. Thank you.

I tried this method now but... not working.

After installing magisk and clicking on reboot, it does not start and is frozen in the unlocked bootloader warning.

Should I install MagiskHide Props Config using TWRP or Magisk Manager?

Remember that the device does not power up, so I can not install it by magisk manager.

Thanks!!
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] KrisM22:
I don't know because I haven't been following this so maybe someone else can answer, but I think it was sometimes you have to install magisk twice. ???

Yes, install magiskhideprops with TWRP. Contrary to what I was doing a few months back (boot to TWRP) where I was trying to catch updates on 8, I

installed

TWRP as I don't need to worry about updates for 9.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] albertovazquez:
What patch of security does this update have for someone who knows
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] milind07:
August security patch
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] albertovazquez:
thanks friend
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] DomBuback:
Hey!

Has anyone managed to root in "

OPNS27.76-12-22-9

" image?

I'm not success!

TWRP not perfectly work and I can't reboot after Magisk install.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Kevinreid1:
Can and does this work for the Verizon Play Droid xt1635-01 model and what if any changes will happen if I flash this rom? thanks
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] KrisM22:
No