Database Users

Be careful with the new multi-stage OTAs.

Google is throwing some multi-stage OTAs that do that, flash stuff on 3 or more stages on recovery. The first one was the full OTA to 7.1.1 Developer Preview 2, and the new one is the incremental OTA from 7.0 november security patch N5D91L to 7.1.1 NMF26F. Those OTAS are captured by normal methods and posted on the forum or on other sites.
I had problems when flashing the DP2 one since apparently you can't sideload those, the recovery does the first stage then sets stage 2/3, reboots and then shows "No command" with 2/3 balls painted, indicating stage 2 of 3, but you can't just continue the flow, adb sideload command crashes at that point and so starting the sideload again starts with stage 1/3 again.. and again.. it's a bucle.
So everyone be careful with these multi staged OTAs, they're sent to devices and installed in some special way, adb sideloading does not work and will get your device stuck on recovery.

RusherDude said:
Google is throwing some multi-stage OTAs that do that, flash stuff on 3 or more stages on recovery. The first one was the full OTA to 7.1.1 Developer Preview 2, and the new one is the incremental OTA from 7.0 november security patch N5D91L to 7.1.1 NMF26F. Those OTAS are captured by normal methods and posted on the forum or on other sites.
I had problems when flashing the DP2 one since apparently you can't sideload those, the recovery does the first stage then sets stage 2/3, reboots and then shows "No command" with 2/3 balls painted, indicating stage 2 of 3, but you can't just continue the flow, adb sideload command crashes at that point and so starting the sideload again starts with stage 1/3 again.. and again.. it's a bucle.
So everyone be careful with these multi staged OTAs, they're sent to devices and installed in some special way, adb sideloading does not work and will get your device stuck on recovery.
Click to expand...
Click to collapse
luckily you have download mode, shud be easy to recover

Google~Android said:
luckily you have download mode, shud be easy to recover
Click to expand...
Click to collapse
Not for those with a locked bootloader that trusted that a sideload verified package would brick them!
Right now the situation is terrible, because the DP2 ota sets the time on 11nov and there is not any full OTA posterior to that (december otas are from 26oct and 1nov!!), and no incremental ota will flash over the mess due to fingerprint and modified boot on stage 1/3.
ADB sideload will soon be dead if all the otas start being multi-staged

RusherDude said:
Not for those with a locked bootloader that trusted that a sideload verified package would brick them!
Right now the situation is terrible, because the DP2 ota sets the time on 11nov and there is not any full OTA posterior to that (december otas are from 26oct and 1nov!!), and no incremental ota will flash over the mess due to fingerprint and modified boot on stage 1/3.
ADB sideload will soon be dead if all the otas start being multi-staged
Click to expand...
Click to collapse
download mode doesn't care if bootloader is locked or not, just flash the firmware and reboot

Google~Android said:
download mode doesn't care if bootloader is locked or not, just flash the firmware and reboot
Click to expand...
Click to collapse
Excuse me, I confused the LG Download Mode with fasboot. But the problem with using the Download mode to flash the TOT files is that the TOT files don't include partitions like vendor and bootloader, and not having an appropiate vendor patition causes even more issues, or you mean even another mode? I'm not well informed on the LG modes

RusherDude said:
Excuse me, I confused the LG Download Mode with fasboot. But the problem with using the Download mode to flash the TOT files is that the TOT files don't include partitions like vendor and bootloader, and not having an appropiate vendor patition causes even more issues, or you mean even another mode? I'm not well informed on the LG modes
Click to expand...
Click to collapse
that all doesn't matter, the available tot is months old I'm thinnking flashing that and then download the latest 7.1.1 ota and flash with recovery and see if it goes, my guess is that it would theres a tutorial of how and where to find and flash the tot.

Google~Android said:
that all doesn't matter, the available tot is months old I'm thinnking flashing that and then download the latest 7.1.1 ota and flash with recovery and see if it goes, my guess is that it would theres a tutorial of how and where to find and flash the tot.
Click to expand...
Click to collapse
Ye I think you mean the bitdomo tutorial:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Maybe it would work, since the phone wouldn't boot anyway thanks to wrong vendor but if it flashes an old system, then you theorically could sideload a newer full OTA. Good idea! That may help people
However, the first step would be to be careful and not flash multi-staged OTAs.. and for Google to not derp like this and block multi-staged OTAs for adb sideload!!!!

RusherDude said:
Ye I think you mean the bitdomo tutorial:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Maybe it would work, since the phone wouldn't boot anyway thanks to wrong vendor but if it flashes an old system, then you theorically could sideload a newer full OTA. Good idea! That may help people
However, the first step would be to be careful and not flash multi-staged OTAs.. and for Google to not derp like this and block multi-staged OTAs for adb sideload!!!!
Click to expand...
Click to collapse
it shud work, and download mode is a great security measure, ive been a lg owner for ther past 5 years and bricked a few devices and was able to recover em via jtag and download mode, vendor is the least of ur issues, dated vendors work but with minor glitches, u forsure would be able to boot system to oem unlock and the be able to unlock the bootloader

Google~Android said:
it shud work, and download mode is a great security measure, ive been a lg owner for ther past 5 years and bricked a few devices and was able to recover em via jtag and download mode, vendor is the least of ur issues, dated vendors work but with minor glitches, u forsure would be able to boot system to oem unlock and the be able to unlock the bootloader
Click to expand...
Click to collapse
Thanks a lot for the help, but I managed to fix it without using the LG tool!!!!!
I discovered a thing:
- When it booted with "Device is corrupt" screen and the boot partition forced to boot always in recovery, the recovery was getting the getprop values (date from the build, fingerprint, device), from the BOOT partition.
- But when you boot recovery DIRECTLY from the bootloader, the recovery gets the getprops values from the SYSTEM PARTITION.
So in this case, since in the stage 1 on the multi stage ota it only affected the kernel, entering from bootloader I was able to flash just the same OTA I had before trying to had the multi stage OTA, since it compared the dates and stuff with the data in the system partition, aka the old data before the fail flash!!
OMG :laugh::laugh::laugh::laugh:

I'm now on N5D91L with unlocked bootloader... so this means I can not sideload the NMF26F downloaded from here?
How is the correct way to upgrade then?

axxel84 said:
I'm now on N5D91L with unlocked bootloader... so this means I can not sideload the NMF26F downloaded from here?
How is the correct way to upgrade then?
Click to expand...
Click to collapse
The site you linked is official site for FULL OTAS, those are intended to be sideloaded so in theory you CAN sideload it
EDIT: Excuse me, I was wrong, you can flash it:
Your 7.0 build (N5D91L) time - Tue Nov 1 18:02:17 UTC 2016 (1478023337)
The 7.1.1 ota (NMF26F) time: Tue Nov 1 18:22:15 UTC 2016 (1478024535)

Thanks RusherDude. Is there another way to update to 7.1 then? I mean, do I need to relock my bootloader and do a factory reset, so I can use OTA update directly by my phone? Or maybe I can do it by using full factory images?

Ext4 [emoji35]
Enviado de meu MB886 usando Tapatalk

axxel84 said:
Thanks RusherDude. Is there another way to update to 7.1 then? I mean, do I need to relock my bootloader and factory reset my phone, so I can use OTA update directly by my iPhone? Or maybe I can do it by using full factory images?
Click to expand...
Click to collapse
Excuse me, I was wrong
Your 7.0 build (N5D91L) time - Tue Nov 1 18:02:17 UTC 2016 (1478023337)
The 7.1.1 ota (NMF26F) time: Tue Nov 1 18:22:15 UTC 2016 (1478024535)
Its actually posterior (by 20mins lol..) so you can sideload it. Sorry confused the times.
Maiselff said:
Ext4 [emoji35]
Enviado de meu MB886 usando Tapatalk
Click to expand...
Click to collapse
Wut?

Help - T Mobile OTA 7.1.2 Update fails with "Error" on Stock Android 7.1.1

Hi,
My 6P is on 7.1.1 Stock Android and I recently unlocked my bootloader, downgraded radio to 3.72 from 3.78 since 3.78 radio was giving LTE issues on T-Mobile. And yesterday, I saw the OTA 7.1.2 update message, so I tried to install, but after re-start, around 30% through the installation process, it suddenly aborts to "Error!". The update availability message again appeared this morning, only to error out again the same way.
I didn't see anyone having similar issue, so wanted to post here to see what could I do.
Thanks

solluidforever said:
Hi,
My 6P is on 7.1.1 Stock Android and I recently unlocked my bootloader, downgraded radio to 3.72 from 3.78 since 3.78 radio was giving LTE issues on T-Mobile. And yesterday, I saw the OTA 7.1.2 update message, so I tried to install, but after re-start, around 30% through the installation process, it suddenly aborts to "Error!". The update availability message again appeared this morning, only to error out again the same way.
I didn't see anyone having similar issue, so wanted to post here to see what could I do.
Thanks
Click to expand...
Click to collapse
OTAs will not install if you have changed any partition. Think of OTAs like a puzzle piece. You can change one side of the puzzle piece by cutting it off to suit your needs, however you have effectively ruined the possibility of the next piece fitting into where you cut off.
Download the Full OTA Image and ADB sideload the OTA. This is the only present form of "OTA" that will install over any user modifications done to the phone. This process will not wipe your phone.
https://developers.google.com/android/ota
Sent from my Nexus 5X using Tapatalk

Thank you. Someone on reddit suggested another option of flashing the radio image for 3.78(which was the one for 7.1.1) and then to try the OTA - Luckily, he uploaded the 3.78 radio image file on gdrive, so I pulled it and succesfully was able to update to 7.1.2.
The issue is that as observed in other threads, only 3.72 radio is the only temporary radio image file which lets me have stable LTE connection on T-Mobile. So, if I want to flash back 3.72 radio image now, for future update I realize that I need to have a 3.81(tied to 7.1.2 build) raido image file as backup. Can you let me know if it's easy for a newbie to understand how to obtain the radio image file? I downloaded 7.1.2 (N2G47J) file from the URL you provided, and it contains radio.modem.img file. Is that it?

I was in the nexus 6p beta program. I am currently suffering the GOOGLE boot loop. Current build on the phone is N2G47i. Out of no where , the phone froze , reboot and just got stuck and never boot pass the GOOGLE boot screen.
I tried to ADB Sideload , but it would not take any file , be it OTA or FUll image that is older than March 8 , as the N2G47i build. is new than the official build. There is no new build newer than March 8 as far as i can tell. My phone is stock non root and bootloader locked. If anyone can assist , I would appreciated.

solluidforever said:
Thank you. Someone on reddit suggested another option of flashing the radio image for 3.78(which was the one for 7.1.1) and then to try the OTA - Luckily, he uploaded the 3.78 radio image file on gdrive, so I pulled it and succesfully was able to update to 7.1.2.
The issue is that as observed in other threads, only 3.72 radio is the only temporary radio image file which lets me have stable LTE connection on T-Mobile. So, if I want to flash back 3.72 radio image now, for future update I realize that I need to have a 3.81(tied to 7.1.2 build) raido image file as backup. Can you let me know if it's easy for a newbie to understand how to obtain the radio image file? I downloaded 7.1.2 (N2G47J) file from the URL you provided, and it contains radio.modem.img file. Is that it?
Click to expand...
Click to collapse
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Good luck...
510jungleboy said:
I was in the nexus 6p beta program. I am currently suffering the GOOGLE boot loop. Current build on the phone is N2G47i. Out of no where , the phone froze , reboot and just got stuck and never boot pass the GOOGLE boot screen.
I tried to ADB Sideload , but it would not take any file , be it OTA or FUll image that is older than March 8 , as the N2G47i build. is new than the official build. There is no new build newer than March 8 as far as i can tell. My phone is stock non root and bootloader locked. If anyone can assist , I would appreciated.
Click to expand...
Click to collapse
Hello... Isn't N2G47H newer than N2G47I ?
Try sideloading 7.1.2 public release: https://dl.google.com/dl/android/aosp/angler-ota-n2g47h-f3bffaba.zip
Supposed to be the latest...
If the above doesn't work, try factory reset from recovery. If your bootloader is unlocked, you can try to flash a full stock image from Google site: https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
If nothing work, you should likely think about RMA your device.
Good luck...

5.1 said:
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Good luck...
Hello... Isn't N2G47H newer than N2G47I ?
Try sideloading 7.1.2 public release: https://dl.google.com/dl/android/aosp/angler-ota-n2g47h-f3bffaba.zip
Supposed to be the latest...
If the above doesn't work, try factory reset from recovery. If your bootloader is unlocked, you can try to flash a full stock image from Google site: https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
If nothing work, you should likely think about RMA your device.
Good luck...
Click to expand...
Click to collapse
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.

510jungleboy said:
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.
Click to expand...
Click to collapse
Ok. Got it. Well... I guess you have to wait next month if you don't want to RMA. Sorry...
Good luck...

510jungleboy said:
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.
Click to expand...
Click to collapse
If you still have a warranty you should RMA your device. Doing a stock OTA update when you are fully on stock with no modifications shouldn't boot loop your phone unless there is something wrong with it. These phones have serious build issues that cause them to permanently bootloop, seemingly out of nowhere. From what I've read people don't generally recover from the type of boot loop you are describing but good luck. If the phone isn't under warranty it's likely time for a new one. The 6P doesn't seem to last very long past the expiration of the warranty.

Thanks for the link
5.1 said:
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Click to expand...
Click to collapse
Hi, thanks for the url, that is really helpful. Also, I realized that, the file is also available in the unzipped version of Nexus 6P Image file. So, it was helpful for me to learn alternatives along with process. :good:

Which stock firmware should I use for an XT1687?

I see over a dozen different versions here but I'm not sure which one to download:
https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I've already tried two different ones but I receive no cell signal when it boots.
Any ideas?
Thanks!

I actually found the answer on my own: none of them. Wrestling with the G5 this morning made me lose my mind. I ended up with the Pixel ROM.

Does anyone have a copy of the XT1687 stock rom (carrier unlocked ... I bought mine at Costco)? I could really use it.
My phone is totally messed up. My /system is empty except for 'bin'....
Thank you for any help!

I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml

dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
did going back to stock and accepting the OTA work for you??!

roydhritiman said:
did going back to stock and accepting the OTA work for you??!
Click to expand...
Click to collapse
I ended up with some kind of error with the OEM partition, but in the end all of the details on my settings screen show that I'm on the latest security patch, kernel, etc.

dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
dunderball said:
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?

dlong said:
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
Patches, a full ROM is rarely sent as an OTA. You'll know it's a full ROM if the size of the OTA is greater than 1GB. Anything less than say 300-400MB is patches to the system

dlong said:
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
I went from version 83 to successful OTA 92 (November patch), then to 93 January patch (but ended up with a failure message after booting up for whatever reason). I'm on retus, baseband M8953_37.46.07.47R POTTER_NA_CUST, build number NPNS25.137-93-4.
As far as I see, I don't see any full stock firmware out for NPNS25.137-93-4 which is unfortunate. I have a feeling my update to Oreo will fail if it ever comes out. I'm not even sure why my OTA fails, as I do my best to avoid modifying any partitions and mostly use systemless modules through Magisk. Whatever though.

No joy. So apparently, since I'm on NPN25.137-92 (POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), I wasn't able to downgrade to (POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
I did re-flash everything and the results seems to be the same (unable to 'see' new updates). I am on November 2017 patch but when I check for upgrades, it states the system is up to date.
I hope that because my phone is 'unlocked from store (Costco - USA)' that RETAIL is the correct firmware. Anyone know for sure?
Also... I guess I wiped recovery when I installed TWRP. Is there an OEM recovery.img available for Moto 5G Plus?
Edit: So the whole reason, I originally rooted my phone was so that I can enable Hot Spot by adding net.tethering.noprovisioning=true to /system/build.prop (now I wonder if root is even required to do that?)

Screwed the pooch this time!!

Hi everyone,I hope someone can help.I recently used the toolkit available to unlock my bootloader,flash twrp and tried to flash a rom.
To say it didnt go to plan would be putting it mildly
Nothing i tried to flash via twrp would actually flash,any rom would fail.
I did eventually get stock reflashed via adb ,still with twrp....had problems with camera and with other apps.
Its working ok now but im stock with october security patch and i cant seem to update it,either by ota or by flashing it
Im on build NPN25.137-92
Baseband m8953_37.46.07.47R POTTER-EMEA_CUST
either id like to get back to fully stock and just wait for the incoming Oreo update or be able to flash a custom rom......help me XDA'ers,your my only hope

Are you running a device with the reteu software channel (I'm guessing so from the EMEA baseband)? If so, the NPN25.137-92 firmware is not for your device - that series of firmwares is for Brazil and Indian devices. EU/US/Asia devices received the NPN25.137-93 series of firmwares (with the latest being NPNS25.137-93-10), so having the incorrect firmware for your device is likely why you are not receiving OTA updates (it's likely the servers don't recognise the combination of your software channel and firmware build).
You can either flash the NPNS25.137-93-4 (Jan 2018 security patch) firmware from here https://forum.xda-developers.com/showpost.php?p=75666258&postcount=3 or the NPNS25.137-93-10 April 2018 security patch firmware from here https://forum.xda-developers.com/g5-plus/development/april-security-patch-xt1687-npns25-137-t3796797 Both should get you back on the OTA update channel, though as always, you may have to lose TWRP (then again, you cannot use OTA updates with TWRP flashed, you need a fully stock and clean device for OTA updates). You could flash TWRP after flashing either of these stock ROMs.
If you do decide to flash either of the aforementioned stock ROMs, please delete the NPN25.137-92 stock ROM and any older stock ROMs from your computer, so you don't accidentally flash an older stock ROM to your device. If you do decide to flash an older stock ROM than the latest firmware on your device, be very careful when using OTA updates; OTA updates on downgraded firmware could cause hard bricks.

Im actually just over the bridge from you in Looe,so im guessing they are very wrong firmwares for me...should of mentioned previously that im in the uk

hippopig said:
Im actually just over the bridge from you in Looe,so im guessing they are very wrong firmwares for me...should of mentioned previously that im in the uk
Click to expand...
Click to collapse
Woo, good to meet you - how's things been in Looe? I imagine really busy given how sunny it's been our way?
Yeah, if you flash either of the NPN25.137-93 series of firmwares, you should be back on the official OTA track for EU/UK firmware (I think that the EU firmware release is the same as the UK), so should get your device back up and running. As for Oreo, we've not seen the soak test beta firmware being tested yet, so we might be waiting a while for the official Oreo.
What errors were you getting btw with TWRP flashing? The error wasn't error 255 by any chance?

Yeah super busy...summer is here woooo,ok ill try and find them tonight and flash it again,I dont think oreo will be coming soon either really......might just flash a custom rom once i can
And yes its error 255 all the time,cant flash anything via twrp at all

hippopig said:
Yeah super busy...summer is here woooo,ok ill try and find them tonight and flash it again,I dont think oreo will be coming soon either really......might just flash a custom rom once i can
And yes its error 255 all the time,cant flash anything via twrp at all
Click to expand...
Click to collapse
Honestly it's up to you - there's reports that soak test invitations have been sent out to Motorola Feedback Network members, so the tests should be happening in the next few weeks. Of course, when the official Oreo OTA will arrive will be dependent on the results of those tests (and what bugs occur).
Hmm, what TWRP version are you using to flash the custom ROMs, and which custom ROMs have you had the issue with?

The problem is that the toolkit twrp is 32bit. You need the latest 64bit twrp to flash anything oreo. I assume you are trying to flash oreo ROMs since most of them are.

on it now,thanks for the replies guys,lol now my pc wont recognise my phone at all

hippopig said:
on it now,thanks for the replies guys,lol now my pc wont recognise my phone at all
Click to expand...
Click to collapse
That's not good - are you in fastboot or ADB when your device isn't recognised? If you're in fastboot, and on Windows 10 or 8.1, try to disable driver signature enforcement (as Microsoft appears to only let signed WHQL drivers load otherwise, which fastboot isn't as far as I know). Have you still got the Motorola USB drivers installed on your computer? If you're using Windows, does your device appear in Device Manager?

Sorry,looks as though its the lead....connecting now

as always,thanks you guys....would be knackered without the support of xda'ers from all over....up and running again on pixel experience

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