Database Users

May security patch now rolling out for XT1092

Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0. The new emoji aren't supported either. Back in Lollipop I also got an update that says Android 5.0.2 but the version stayed at 5.0 after the update. Anyways, this update is 15MB and takes around 20 minutes to install, contrary to what Motorola says.
Also, really Motorola? MAY?! I'd be expecting you to roll out the QuadRooter (August/September) patch by now.

Hi,
thnx for the info.
Any suggestions if anyone is making update zip for twrp installation?
Regards
LK82

Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?

YassGo said:
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
Click to expand...
Click to collapse
I think these official updates fail if you are rooted.... but if it succeeds i don't know if you retain root.

Again the RetGB variant being overlooked apparently. Spanish version got it and British version nothing...

Do anyone have some changelog for this security update? Does it fix Bluetooth issues (sometimes not routing audio via BT when connected to Nokia car kit)?

AB__CD said:
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0.
Click to expand...
Click to collapse
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Hello
This weekend I got a prompt on my phone (model XT1092) to upgrade to android 6.0.1.
I was happy about this upgrade because it solves a bug that prevented me from using bluetooth tracking devices [1].
However, after the upgrade the android version mentioned in the phone settings is still 6.0 and not "6.0.1" as expected. The only change I notice is that the "security patch" level is now May 1 2016.
Please confirm which version is actually is and/or if the specific bluetooth low-energy fix mentioned in link [1] is included.
Thanks
Click to expand...
Click to collapse
[1] URL can't link to in this forum, but search for "tileapp 6.0.1" in google

No OTA when rooted.
My MOTOX is rooted and has TWRP, so no OTA possible.
Any chance of this upgrade being downloadable somewhere alreadY?

bart.cerneels said:
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Click to expand...
Click to collapse
I can confirm that notification says "New version: 24.201.3.en.EU" and "Android 6.0.1, Marshmallow".
OK, in OP there is a screenshot with 6.0 still. So no go for BT patch I think...

Screenshot Android 6.0.1 promt
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.

sgpieter said:
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
Click to expand...
Click to collapse
Yeah, Motorola might just as well be Chinese now.

maybe this helps someone
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
Click to expand...
Click to collapse
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody

JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
Hi, could you possibly upload the OTA file you downloaded? Could come in handy
Thnx in advance.
Cheers
Sent from my MOTO X using XDA Labs

As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3

JonesMuc said:
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
Click to expand...
Click to collapse
Thnx m8, really appreciated:good:
Cheers
Sent from my MOTO X using XDA Labs

JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
May you tell the name of the post after searching "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1" ?
or some clues,
smthg plz ?
I suppose this is for rooting again
I'm looking for the stock recovery.img and the stock boot.img.
May you tell what to search to obtain them plz ?
Thx

You can find the recovery.img and boot.img in any stock firmware.
I used one from this site because it had the same version as mine:
androidsage.com/2016/02/09/install-official-marshmallow-ota-for-moto-x-android-6-0-ota-capture/
When you google for "blur_version.24.11.18" (or the version you need) you will find a lot of firmwares to download.
You are right, the other post is just for rooting again, after you updated

OK, thx :good:

Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha

theoblackhawk said:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
Click to expand...
Click to collapse
One word: Lenovo
Actually four words: Lenovo being an ass

XT-1644 Official Nougat Update?

My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png

You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.

echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?

waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612

echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.

waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.

update to android O using flashfire

Hi guys
Currently, i have a nexus 6p, 7.1.2, rooted and bootloader unlocked.
Got the android O ota updates on my phone. however, wanted to know is it safe to upgrade now using flashfire?
1st, any problems when using flashfire to do the updates
2nd, any problems on android O itself?
3rd, do i still have root after the udpate?
Thanks.

mousefai0922 said:
Hi guys
Currently, i have a nexus 6p, 7.1.2, rooted and bootloader unlocked.
Got the android O ota updates on my phone. however, wanted to know is it safe to upgrade now using flashfire?
1st, any problems when using flashfire to do the updates
2nd, any problems on android O itself?
3rd, do i still have root after the udpate?
Thanks.
Click to expand...
Click to collapse
There is a thread on this ongoing at literally this moment. My experience is that FF with the OTA does not work. Others have reported that it does. So YMMV. The fastboot method worked for me. FF with full factory images may work, but since radio is still recommended to be flashed via fastboot you might as well do everything via fastboot.

mousefai0922 said:
Hi guys
Currently, i have a nexus 6p, 7.1.2, rooted and bootloader unlocked.
Got the android O ota updates on my phone. however, wanted to know is it safe to upgrade now using flashfire?
1st, any problems when using flashfire to do the updates
2nd, any problems on android O itself?
3rd, do i still have root after the udpate?
Thanks.
Click to expand...
Click to collapse
I was trying FF this morning, lastest update 0.71, rooted with Magisk , TWRP and it failed.
Got stuck on a black screen for more than five minutes until I forcefully rebooted the device.
waiting for the factory images I guess.

wizardwiz said:
I was trying FF this morning, lastest update 0.71, rooted with Magisk , TWRP and it failed.
Got stuck on a black screen for more than five minutes until I forcefully rebooted the device.
waiting for the factory images I guess.
Click to expand...
Click to collapse
it seem like the android O have bugs and problem itself, and with now the failing flashfire problems... i think i should wait

GroovyGeek said:
There is a thread on this ongoing at literally this moment. My experience is that FF with the OTA does not work. Others have reported that it does. So YMMV. The fastboot method worked for me. FF with full factory images may work, but since radio is still recommended to be flashed via fastboot you might as well do everything via fastboot.
Click to expand...
Click to collapse
it seem like the android O have bugs and problem itself, and with now the failing flashfire problems... i think i should wait

I just used FF ver. 0.72 on 2 rooted, twrp'd, supersu'd Nexus 6P's and flashed the full factory Sept. 2017 OPR6 image that was published this morning. FF worked like a champ. Just don't update the bootloader and radio with FF.

I am still on 6.0.1 (Build MTC20L), upgraded using FF. If i want to move to 8.0.0 (OPR6.170623.017, Sep 2017), what builds do I need to stop at along the way? I was guessing at the very least 7.1.1 (NUF26N, Mar 2017, Verizon Only), but want to be sure.

states_enemy said:
I am still on 6.0.1 (Build MTC20L), upgraded using FF. If i want to move to 8.0.0 (OPR6.170623.017, Sep 2017), what builds do I need to stop at along the way? I was guessing at the very least 7.1.1 (NUF26N, Mar 2017, Verizon Only), but want to be sure.
Click to expand...
Click to collapse
No, just use the latest full Google 8.0 image with FF. Untick the bootloader and modem partitions. Your phone will boot up with 8.0, then update the bootloader and modem (radio) separately. Best to flash with fastboot, but there are TWRP flashable zips around here.

v12xke said:
No, just use the latest full Google 8.0 image with FF. Untick the bootloader and modem partitions. Your phone will boot up with 8.0, then update the bootloader and modem (radio) separately. Best to flash with fastboot, but there are TWRP flashable zips around here.
Click to expand...
Click to collapse
I'll be using FF, however I don't recall ever updating the bootloader or modem in the past. I don't need to do that, do I?

states_enemy said:
I'll be using FF, however I don't recall ever updating the bootloader or modem in the past. I don't need to do that, do I?
Click to expand...
Click to collapse
You know what they say about not fixing it if it's not broken, but.... While bootloader and modem are independent of the android version itself, you should generally try to keep them up to date. Not sure how a bootloader would be improved, but there are constant tweaks to the radio going on. If you don't have a current, working version of ADB/fastboot on your PC this would be a good time to get it set up and working properly ( ie. when you are NOT having a problem). There is virtually no way you can screw up flashing these, and they take less than a second or two each. You can find the *.img files in the root of any full Google image. As a primer, open up the flash-all.bat file there and read the script. Change the file extension from *.bat to *.txt and open with Notepad. There you will find the fastboot commands for flashing these two. Best of luck.

[mini-GUIDE] BRICKED / DOWNGRADE / SAME / UPGRADE - also ALTERNATIVE to RSDlite

I am not responsible for your bricked phone or pigeon poo on your toupe. Do at your own risk.
Many thanks to @SupahCookie for idea and motivation!
INTENTIONALLY DOES --NOT-- LOCK BOOTLOADER!!!
Get factory images here:
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
THIS GUIDE IS FOR FACTORY/STOCK ROMs - NOT YOUR AVERAGE CUSTOM ROM which may not have bootloaders!!! (thanks!!!!! @echo92 )
FIX:
IF YOU ARE ABLE TO GET TO FASTBOOT THIS SHOULD WORK.
IF YOU HAVE 8.x bootloaders AND ARE DOWNGRADING TO 7, use "Alternative to RSDlite" below.
1 boot to win - 7 or 10 works fine.
2 boot phone to fastboot, and connect phone to computer.
3 start RSDlite
pick a ROM. I believe I used a 7.1.1 rom
3Nov9-ADDISON_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RSDlite installed it and fixed the problem.
- -
I was then able to use RSDlite to install @rafikowy 's signed 8.0 . - going up from 7 to 8.
- -
- -
If you are on 8.x bootloaders and want to go to 7.x bootloaders, use this (RSDlite throws an error and stops):
ALTERNATIVE TO RSDlite:
1 I used 7zip to extract that 7.1.1 zip (or any ROM zip) into a folder x,
2 add all the adb and fastboot junk to folder x,
3 add the attached file (rename it to flash.bat) to folder x.
4 boot phone to fastboot and connect to computer.
5 click on flash.bat - it throws a lot of "slot" errors but works just fine.
6 reboot your phone if it hasn't already and go through the 7.x install stuffs.
7 you will not show an IMEI if you are coming from an 8.x bootloader. However, it IS there.
NOTE: you may need to add a line to the flash.bat if there are more/less sparsechunk's in your FACTORY/STOCK ROM...
THIS IS NOT FOR CUSTOM ROMs!!!!!!!
EDIT: 3-8-19: I just did this myself to go back very briefly to 7.1 - be sure you don't flash TWRP to it if your going to take OTAs - it will brick it. boot to TWRP if you need TWRP briefly: fastboot boot twrpimg.img
----------
If you can boot to fastboot screen, you can do anything.
Never OTA a ROM if you have modified recovery (TWRP, etc) or if magisk is present.
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
I changed the attached file to add pause and reboot and exit to make it slightly more automated.

I have successfully used this many times going back and forth. If you can boot to fastboot screen, you can save your phone and flash anything you want.

You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.

echo92 said:
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
Click to expand...
Click to collapse
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!

KrisM22 said:
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
Click to expand...
Click to collapse
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?

echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
YES - that's why I wrote these 3 guides - before, it was quite possible to wind up with a bootloader mix - esp depending on the zip you use! - factory/stock only!!!
I added a line to the guide saying that it is only intended to be used for the factory/stock zips as these have (I believe) the bootloaders appropriate to the ROM.
Many thanks for pursuing this! - I wonder if we'll have to exclude certain ROMs that are in the factory lists?????

echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device
Click to expand...
Click to collapse
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.

KrisM22 said:
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
Click to expand...
Click to collapse
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.

echo92 said:
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
Click to expand...
Click to collapse
Downgrading is a piece of cake if you don't use RSDlite - it throws an error and stops. Using the bat file it can happily throw all the errors it wants and all I care is at the end I have what I want.
It does indeed change the entire environment when you bat file the zip contents. You can bat file to get from 8 to 7 and then use RSDlite to flash a different 7 OR 8 zip file. There is no resulting difference in whether you RSDlite it or bat file it - the bat file simply comes from the .xml file that is within the zip. There is very little or no difference between that among addison factory/stock zips. Other zips are different (custom ROMs.)
Grab any factory/stock zip for addison and expand it and you will see modems, bootloaders, indeed absolutely everything you would find on that phone if you went to a store and bought it. SupahCookie simply added a couple lock command lines because it was intended for folks who somehow thought that if phone was locked they could take it back to the store and get their money back. Or some such. I found that ATT folk didn't care if you were on CM or whatever if you just needed to swap SIMs or whatever.
I DON'T want to lock the phone as it prevents me from modifying forever. Oh yeah that reminds me I was going to post the obligatory guide (again) about how to flash a white boot logo so you don't get that message - it's still there LOL but since the font is in white, you can't see it.

I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?

Necrowr said:
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Click to expand...
Click to collapse
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!

KrisM22 said:
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
Click to expand...
Click to collapse
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead

Necrowr said:
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Click to expand...
Click to collapse
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
or
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
might have some stock ROMs of interest...

KrisM22 said:
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
might have some stock ROMs of interest...
Click to expand...
Click to collapse
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD

Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
Custom ROMs won't usually update the bootloader (even if they are newer) as stock ROMs typically only have the bootloader firmware.
You could look into flashing the stock Oreo albus 8.0 ROM https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 or the 8.0 June 2018 firmware https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 but please check that firmware has been released for your device variant.
I don't know if updating your baseband to stock Oreo formally may fix your IMEI issue.

Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)

KrisM22 said:
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
Click to expand...
Click to collapse
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.

Necrowr said:
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Click to expand...
Click to collapse
If you flashed a stock O that would have changed bl to O, but doing the above with the stock 7.1.1 would have changed them back to N. No matter (other than academic) that you don't remember the path - flashing a stock anything reverts it to that point in time. However, IMEI may have been moved - don't know. It will likely show on EITHER 7.x or 8.x stock - just don't know which.
If you flash a stock 8.x from those links I gave you above, it should offer you ota, ASSUMING there are any at this point in time(Z has 2). Adding Magisk at any point seems to hose you for receiving any more ota's - don't understand why, even with magisk uninstall, so that would mean going back to the latest stock and losing what you have (which is why I try to take a TBPro and copy that backup to PC (because re-flashing 8.x stock will likely reset internal storage.).
yes, if you enter stock recovery, you are likely at stock, though you could reflash the latest 7 or 8 stock to be sure, depending on which you want to use as base. Since 8 is having security fixes released, I choose 8 and will likely have no more interest (no time!) in 7.

So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.

Necrowr said:
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Click to expand...
Click to collapse
did it offer to let you d/l it again? you could try that.
However, there exist O stock zips in those links I gave you so you could just flash the latest...

Final Official Oreo 8.1.0 Release - OPP28.85-16 OTA

I've just captured the Official OPP28.85-16 OTA for retail cedric and I'm posting it here. I'm on retbr channel but this will work on any retail device. If you're on another updated channel, I don't know what would happen if you installed this.
Notice that to install this YOU MUST be on NPPS25.137-93-2-5 to install these, since OTA's are not full firmwares like fastboot files, but instead they're patchings tailored to be applied upon a specific firmare - NPPS25.137-93-2-5 in this case.
Another particular detail is that the OTA file (gotten directly from my credric) lists the Blur Version as Blur_Version.25.361.10.cedric.retail.en.US, but curiously, the fastboot version for the same firmware ( which you can download here) lists it as Blur_Version.28.41.15.cedric.retail.en.US
Someone also reported in another thread that they just sideloaded this upon the Second Soak test. I wouldn't doubt it since this is what should happen to regular soak testers, but if you do it, DO IT AT YOUR OWN RISK
I also won't post instructions on how to install this since they're already available here
Download
Gdrive: https://drive.google.com/file/d/149hrGFpuWUgAvJr02McYNwJVaqSvllYO/view?usp=sharing
That's it.

changelog?

Has anyone already tried it?

Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
Someone also reported in another thread that they just sideloaded this upon the Second Soak test.
Click to expand...
Click to collapse
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.

JoeDoe0 said:
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it

Works perfect
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018

bori321 said:
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
Click to expand...
Click to collapse
On which version you were before update?

Firmware
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...

Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
freeZbies said:
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Click to expand...
Click to collapse
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.

JoeDoe0 said:
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
Click to expand...
Click to collapse
yeah, I actually misread it, now I see it.
Anyways, flashing it from fastboot doesn't prove anything. but seems like Cedric can be upgraded from the soak test to final version using this ota. Idk because I used fastboot myself too, since I had already modified my system partition.

AsusZenFone3Deluxe said:
changelog?
Click to expand...
Click to collapse
seriously?
stop joking, Motorola doesn't release changelogs.
but I'll try:
updated from nougat to oreo?
duhhh

how is speaker quality in this build ?
because there is some issues in previous oreo builds

Speaker
Hi,
i would say that for my ears the speaker sounds better than it was with Nougat.
After a few days of testing everything works really good and i have not found anything not working or any problems.
Alex

bori321 said:
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Click to expand...
Click to collapse
how do you get back to NPPS25.137-93-2-5

I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
- back to NPPS25.137-93-2-5 via the commands from the thread i linked (without the lines:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
)
- via ADB sideload with the Oreo download from this thread to Oreo.
Alex

ahmedAZ said:
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Click to expand...
Click to collapse
In my experience the quality is better than on previous oreo builds.
ahmedAZ said:
how do you get back to NPPS25.137-93-2-5
Click to expand...
Click to collapse
if you have an unlocked bootloader download NPPS25.137-93-2-5 Flashable Zip here and flash it with twrp
bori321 said:
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
Alex
Click to expand...
Click to collapse
to flash official Motorola files there's no need to unlock the bootloader.
you've just unnecessarily voided your warranty

@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117

Chekm8Qc said:
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Click to expand...
Click to collapse
I dont know if the twrp version would be valid. To apply an OTA, your system must matchbit by bit, so the most guaranteed way is to flash that firmware via fastboot, but you could try flashing the twrp version, and in case it works, you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot

freeZbies said:
I dont know if the twrp version would be valid. To apply an OTA, your system must match stick bit by bit, so the most guaranteed way is to flash that firmware via fastboot, but. you could try flashing the twrp version, and in case it. woeks you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
Click to expand...
Click to collapse
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.

Chekm8Qc said:
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Click to expand...
Click to collapse
being soft bricked doesnt necessarily mean you can recover it through twrp. OTA's are different of twrp flashables in that it modifies things beyond system partition. I've seen reports from people with other motorola devices who applied an OTA while having a modified system partition, and even though they were able to boot to twrp, flashing a custom Rom or restore a backup wouldn't make the phone boot. Their phones weren't hard bricked, but still they had to fastboot to recover their phones. Anyways, why don't you flash the Twrp flashable if, it's already available (considering you have an unlocked bootloader).
I'm case you have a locked bootloader you may fastboot without executing "fastboot erase userdata" in case you want to try. I did it without losing my data (although I was already in Opp 28.85-16)
but after all I really advice you to flash the twrp zip if u can