I wanted to unlocked my bootloader so I can flash custom mods and modify the system partition without losing Android Pay and other apps while staying on stock kernel and unrooted. So, I made this kernel for myself, and I thought I'd share it with the community.
Stock kernel with safetynet unlocked bootloader patch (new updated patch), and dm-verity disabled so the system partiton can be modified.
Download:
8.1:
Mar2018 security update: android-msm-marlin-3.18-oreo-mr1-safteynet-dmverity-patch-mar2018
Feb2018 security update: android-msm-marlin-3.18-oreo-mr1-safteynet-dmverity-patch-feb2018
Jan2018 security update: android-msm-marlin-3.18-oreo-mr1-safteynet-dmverity-patch-jan2018
Dec2017 security update: android-msm-marlin-3.18-oreo-mr1-safteynet-dmverity-patch-dec2017
Developer Preview 1: android-msm-marlin-3.18-o-mr1-preview1-safteynet-dmverity-patch
8.0.0:
Nov2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-nov2017
Oct2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-oct2017
Sep2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-sep2017
Source:
Github
reddv1 said:
I wanted to unlocked my bootloader and flash custom mods and themes without losing Android Pay and other apps while staying on stock kernel and unrooted. So, I made this kernel for myself, and I thought I'd share it with the community.
Stock kernel with safetynet unlocked bootloader patch (new updated patch), and dm-verity disabled so the system partiton can be modified.
Download:
8.0.0:
Oct2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-oct2017
Sep2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-sep2017
Source:
Github
Click to expand...
Click to collapse
What version? For fi/us or the canadian version
Sent from my Pixel XL using Tapatalk
jay661972 said:
What version? For fi/us or the canadian version
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
The Oct2017 kernel is for all October builds, and Sep2017 is for the September builds. It doesn't matter what build you're on, the kernels are the same.
Sent from my Pixel XL using Tapatalk
reddv1 said:
The Oct2017 kernel is for all October builds, and Sep2017 is for the September builds. It doesn't matter what build you're on, the kernels are the same.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thank you.
Sent from my Pixel XL using Tapatalk
Update posted to OP for November 2017 security patch
Does this have support for kernel modules?
gudenau said:
Does this have support for kernel modules?
Click to expand...
Click to collapse
Yes, it's enabled in the config file when building the kernel, but I've never tested loading a module myself.
Sent from my Pixel XL using Tapatalk
reddv1 said:
Yes, it's enabled in the config file when building the kernel, but I've never tested loading a module myself.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Cool!
I have no idea what I wanted to do with a module before, but that's good to know.
Can someone make this more user friendly by making a backup of their boot image in img format so it can be flashed in unified toolkit for people who ain't really so fastboot/adb friendly this I appreciate the unlock but it's missing directions.. all it implies is the fastboot commands how is anyone who is new to Android supposed to know what to do with this... I think a boot.img which can be flashed in unified toolkit would be better for everyone half the people new looking at this like oh ok why isn't it a boot.img
---------- Post added at 06:46 PM ---------- Previous post was at 05:52 PM ----------
Also the idea was a stolen idea and no credit was given so I feel like no credit should be given here in regards to the unlocked bootloader.. before that one dude posted his unlocked bootloader boot image method this boot image here was just a root and safety net image there was nothing in it in regards to a unlocked bootloader.. it was a stolen idea and this person is trying to take credit for work which he didn't come up with I mean damn all you did was sign the boot image which he posted and added safety net and now I guess you want to claim credit?
Update posted to OP for 8.1 Developer Preview 1.
I'll post an update for Preview 2 as soon as Google releases the source. Preview 1 kernel might work on Preview 2, but I haven't tested it.
Update posted to OP for Android 8.1 December 2017 security patch
Do I need to sign it or something? When I flash it I get bootloops.
hackthis02 said:
Do I need to sign it or something? When I flash it I get bootloops.
Click to expand...
Click to collapse
No, you don't have to sign it, because you are flashing the kernel directly and not the boot.img.
Did you follow the Fastboot command (fastboot flash kernel marlin-8.1.0_r0.4.lz4-dtb)? Make sure you only flash over the stock boot.img. I haven't tested flashing over a custom kernel or TWRP, Flash TWRP after if you want.
That's all I can think of at the moment, I've flashed it and works perfectly fine.
Sent from my Pixel XL using Tapatalk
reddv1 said:
No, you don't have to sign it, because you are flashing the kernel directly and not the boot.img.
Did you follow the Fastboot command (fastboot flash kernel marlin-8.1.0_r0.4.lz4-dtb)? Make sure you only flash over the stock boot.img. I haven't tested flashing over a custom kernel or TWRP, Flash TWRP after if you want.
That's all I can think of at the moment, I've flashed it and works perfectly fine.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. I was doing fastboot flash boot marlin-8.1.0_r0.4.lz4-dtb.
Will this work with My GPXL Verizon on A 8.1.0?
dyingjedi said:
Will this work with My GPXL Verizon on A 8.1.0?
Click to expand...
Click to collapse
Yes
Sent from my Pixel XL using Tapatalk
I'm getting:
(bootloader) flash size too large
Will the Dec. work for the January security patch?
xomikronx said:
Will the Dec. work for the January security patch?
Click to expand...
Click to collapse
Probably would work, it's only a security update, but I haven't tested it. Also, the January source hasn't been released yet so I can't check it or build the new kernel.
Sent from my Pixel XL using Tapatalk
kd0g said:
I'm getting:
(bootloader) flash size too large
Click to expand...
Click to collapse
Are you flashing over a custom kernel or TWRP? If so, the ramdisk might be too big. Try flashing the stock boot image then flashing this kernel.
Sent from my Pixel XL using Tapatalk
Related
https://developers.google.com/android/nexus/images
5.1.1 (LMY48X) https://dl.google.com/dl/android/aosp/mantaray-lmy48x-factory-c955bd95.tgz
Md5 641500e561efcf5285de508fe453d84c
Update:
5.1.1 (LMY48Z) https://dl.google.com/dl/android/aosp/mantaray-lmy48z-factory-584a4d03.tgz
Md5 7d00c2fb6ed5b40222cd8a42e2d6a740
At least we still get security updates
Sent from my XT1575 using Tapatalk
Darnell_Chat_TN said:
At least we still get security updates
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
lets see for how long
stunned said:
https://developers.google.com/android/nexus/images
5.1.1 (LMY48X) https://dl.google.com/dl/android/aosp/mantaray-lmy48x-factory-c955bd95.tgz
Md5 641500e561efcf5285de508fe453d84c
Update:
5.1.1 (LMY48Z) https://dl.google.com/dl/android/aosp/mantaray-lmy48z-factory-584a4d03.tgz
Md5 7d00c2fb6ed5b40222cd8a42e2d6a740
Click to expand...
Click to collapse
How do I flash the december update? I am on rooted Android 5.1.1 (LMY48X) with TWRP custom recovery. There is no " image" extension in the tgz archive.
elgar said:
How do I flash the december update? I am on rooted Android 5.1.1 (LMY48X) with TWRP custom recovery. There is no " image" extension in the tgz archive.
Click to expand...
Click to collapse
For example use Wugfresh to install factory image without wiping data
stunned said:
For example use Wugfresh to install factory image without wiping data
Click to expand...
Click to collapse
Will xposed framework prevent from flashing via nexus root toolkit? Because I am doing it, but with no success.
I have a nexus 6 on LMY48X?
elgar said:
Will xposed framework prevent from flashing via nexus root toolkit? Because I am doing it, but with no success.
Click to expand...
Click to collapse
Of course. What made you think it wouldn't cause issues?
Sent from my Nexus 9 using Tapatalk
Installed flawlessly with Wugfresh!
Here it is
Factory
https://dl.google.com/dl/android/aosp/angler-n4f26o-factory-c53f0a50.zip
Factory
https://dl.google.com/dl/android/aosp/angler-nuf26k-factory-bde381d4.zip <------ VERIZON ONLY
OTA
https://dl.google.com/dl/android/aosp/angler-ota-n4f26o-6a853f19.zip
OTA
https://dl.google.com/dl/android/aosp/angler-ota-nuf26k-baec5b5e.zip <------ VERIZON ONLY
cheers
N4F26O
Baseband 3.78
Kernel 3.10.73 (Dec 7)
Patch Level: Feb 5
Bootloader 3.64
https://source.android.com/security/bulletin/2017-02-01.html
Both N4F26O:
Fac image with encryptable boot-kernel:
https://www.androidfilehost.com/?fid=673368273298929182
Encryptable boot-kernel only:
https://www.androidfilehost.com/?fid=673368273298929179
so we just flash this and it will not affect anything on my phone? im rooted stock rom and franco kernel
Someone correct me if I'm wrong but I think it replaces the recovery which you can just put back. You'll also lose root I think which again you could just flash. At least that's how it was for the stock roms I've dealt with on other phones.
jaron7_11 said:
so we just flash this and it will not affect anything on my phone? im rooted stock rom and franco kernel
Click to expand...
Click to collapse
what do you have installed?flashfire or TWRP
danmaman said:
what do you have installed?flashfire or TWRP
Click to expand...
Click to collapse
Twrp
jaron7_11 said:
Twrp
Click to expand...
Click to collapse
you can use this guide
http://elementalx.org/how-to-install-android-monthly-security-updates/
cheers
Good to have... for now
danmaman said:
you can use this guide
http://elementalx.org/how-to-install-android-monthly-security-updates/
cheers
Click to expand...
Click to collapse
That one doesn't mention the radio. I prefer to use Heisenberg's guide. Usually #14 for when I'm flashing updates but there's a lot of other useful tips as well.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hi there! Does this have any fixes or is it just security stuff? I'd like to know if the echo during a hangouts/Skype/Duo call gets any better. Thanks!
Sent from my Nexus 6P using Tapatalk
Pig Vomit said:
N4F26O
Baseband 3.78
Kernel 3.10.73 (Dec 7)
Patch Level: Feb 5
Bootloader 3.64
https://source.android.com/security/bulletin/2017-02-01.html
Click to expand...
Click to collapse
on January Factory [N4F26J]image our Baseband/Radio is 03.79
the latest February Factory [N4F26O]image is Baseband/Radio is 03.78
downgrade?
fLipz said:
on January Factory [N4F26J]image our Baseband/Radio is 03.79
the latest February Factory [N4F26O]image is Baseband/Radio is 03.78
downgrade?
Click to expand...
Click to collapse
Yes it seems so..... Weird
Looks like radio version is downgraded !!?
I use FlashFire and it keeps TWRP and ROOT
fLipz said:
on January Factory [N4F26J]image our Baseband/Radio is 03.79
the latest February Factory [N4F26O]image is Baseband/Radio is 03.78
downgrade?
Click to expand...
Click to collapse
Last month people speculated that N4F26I with radio 3.78 was for non-Verizon and N4F26J with radio 3.79 was for Verizon because it fixed VOLTE and Voicemail for Verizon customers. Perhaps they just neglected to label last month? I note the new Verizon-only NUF26K keeps the 3.79 radio.
I'm on T-Mobile and last month was running 26J with 3.79 radio and had no problems. Now on 26O with 3.78 and having no problems.
My 6P got the I version last month. I suppose the J was only for the US provider Verizon because I didn't see anyone I know with a 6P to receive the J version.
Do someone know is there a pixel mod for February images?
rnavass said:
Do someone know is there a pixel mod for February images?
Click to expand...
Click to collapse
I applied an older version, it seems to be working but I am getting a weird message on boot "Internal error in your device" or something similar to that.. weird.
I mean it's all working alright , just this message on boot.
EDIT:
OK the exact error was "There's an internal problem with your device. Contact your manufacturer for details"
It was an error in the prop.build file. Mismatch with the vendor prop.build file.
Copied the value :ro.build.fingerprint from the vendor file to the prop.build under system and it disappeared.
wizardwiz said:
I applied an older version, it seems to be working but I am getting a weird message on boot "Internal error in your device" or something similar to that.. weird.
I mean it's all working alright , just this message on boot/
Click to expand...
Click to collapse
Which one did you flash it?
May security patch is out. Google factory images is alive
https://developers.google.com/android/images#angler
I just got the OTA pushed out to me. It is dated 5th may
pemz82 said:
I just got the OTA pushed out to me. It is dated 5th may
Click to expand...
Click to collapse
Hilarious. Just checked and you're right. used the factory images and it's May 5th
wizardwiz said:
Hilarious. Just checked and you're right. used the factory images and it's May 5th
Click to expand...
Click to collapse
That's because there are usually two security patches, and they are usually dated the 1st and the 5th. One is a partial string and one is complete. You can read about the differences and why there are two on the Android security blog. In short, supported Google devices get the complete security patch level string dated the 5th.
v12xke said:
That's because there are usually two security patches, and they are usually dated the 1st and the 5th. One is a partial string and one is complete. You can read about the differences and why there are two on the Android security blog. In short, supported Google devices get the complete security patch level string dated the 5th.
Click to expand...
Click to collapse
Sorry for the noob question but N2G47O is not the full rom image to flash over fastboot?
jsecruzvalencia said:
Sorry for the noob question but N2G47O is not the full rom image to flash over fastboot?
Click to expand...
Click to collapse
Well yes and no. The build number is the same for both the full image and the OTA. If you received the update via OTA, then it is not the full image- it is a smaller incremental update package. If you want the full Google image you can find it here. There are instructions on that page on how to fastboot flash. If you want to flash this update without wiping your data, open up the flash-all.bat file with Notepad and remove the "-w" switch, save it and close. Make sure you are using the latest adb/fastboot binaries.
v12xke said:
Well yes and no. The build number is the same for both the full image and the OTA. If you received the update via OTA, then it is not the full image- it is a smaller incremental update package. If you want the full Google image you can find it here. There are instructions on that page on how to fastboot flash. If you want to flash this update without wiping your data, open up the flash-all.bat file with Notepad and remove the "-w" switch, save it and close. Make sure you are using the latest adb/fastboot binaries.
Click to expand...
Click to collapse
Thanks a lot
Do we know what this patch updated/fixed?
Pain-N-Panic said:
Do we know what this patch updated/fixed?
Click to expand...
Click to collapse
Published monthly:
https://source.android.com/security/bulletin/2017-05-01
Someone hav or where to find a stock flashable rom?
Thx in advance
Sent from my Google Nexus 6P using XDA-Developers Legacy app
jujak82 said:
Someone hav or where to find a stock flashable rom?
Thx in advance
Sent from my Google Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://www.google.ca/search?q=stoc.....69i57j0l4.5419j0j7&sourceid=chrome&ie=UTF-8
1st line.
jujak82 said:
Someone hav or where to find a stock flashable rom?
Thx in advance
Sent from my Google Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
If you mean flashable with twrp, you can download and unpack the factory image, and flash the boot,system and vendor.img with twrp.
Dumb question time: Is there a zip of this patch that I can flash via TWRP that won't lose root? I'm on the stock ROM updated to the April security patch right now.
Sorry for the noob question, haven't rooted a phone since before Google started pushing monthly patches. Thanks in advance!
BAMF said:
Dumb question time: Is there a zip of this patch that I can flash via TWRP that won't lose root? I'm on the stock ROM updated to the April security patch right now. Sorry for the noob question, haven't rooted a phone since before Google started pushing monthly patches. Thanks in advance!
Click to expand...
Click to collapse
Do yourself a favor and Install Flashfire. Ignore OTAs. Download the latest full image from Google and use Flashfire to install. Select only the boot, system and vendor partitions. It will preserve your root and recovery. Once in a blue moon when there is a new bootloader and/or modem, you can flash those manually. This is a very safe, two minute update once a month. Note: Because you are flashing a new boot.img, you will naturally lose any custom kernel you had installed. Simply reflash it after the update if you had one. More info here.
Whoever downloaded this rom in full, could u please extract the recovery.img for me?
Sent from my Nexus 6P using XDA-Developers Legacy app
zukriaksah said:
Whoever downloaded this rom in full, could u please extract the recovery.img for me?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Here you go,
https://www.dropbox.com/s/v1izmllmyeohxap/recovery.img?dl=0
Fe Mike said:
Here you go,
https://www.dropbox.com/s/v1izmllmyeohxap/recovery.img?dl=0
Click to expand...
Click to collapse
Thank you very much!
Sent from my Nexus 6P using XDA-Developers Legacy app
Since no one asked yet I'll ask. Lately Google will release two, one for Verizon and one for the rest. So far no image for Verizon, anyone try this on Verizon yet?
Fe Mike said:
Since no one asked yet I'll ask. Lately Google will release two, one for Verizon and one for the rest. So far no image for Verizon, anyone try this on Verizon yet?
Click to expand...
Click to collapse
There was a short period where there were two different images.
I'm using stock 7.1.2 with the May security patch. No issues.
tech_head said:
There was a short period where there were two different images.
I'm using stock 7.1.1 with the May security patch. No issues.
Click to expand...
Click to collapse
Thank you. Just curious, so if you're on 7.1.1 and have may security patch did you only flash the bootloader and radio only out of the image? I only ask because may is 7.1.2. Sorry for noob questions, this is the first phone I've ever had that has unlockable bootloader. I always had a Verizon galaxy phones that were locked down.
how to? hahaha
same problem it was before "only official release binaries are allowed to be flashed"
only now I have no BL "A520FXXU3" to power flash with the December att patch
caiquess95 said:
how to? hahaha
same problem it was before "only official release binaries are allowed to be flashed"
only now I have no BL "A520FXXU3" to power flash with the December att patch
Click to expand...
Click to collapse
Follow the same procedure as below:
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Cannot bro. Until now, only the December security update use "level 3" block bootloader. So cannot use BL of other lower firmware. November security update use the same "level" bootloader with lastest MM update ("level" 2).
thangluong said:
Cannot bro. Until now, only the December security update use "level 3" block bootloader. So cannot use BL of other lower firmware. November security update use the same "level" bootloader with lastest MM update ("level" 2).
Click to expand...
Click to collapse
Worked for me. I have rooted mine using the same process by flashing below combination:
BL: A520FXXU2AQFA
AP+CP+CSC: All from Dec. 18 nougat build (QLA)
waltermsalomon said:
Worked for me. I have rooted mine using the same process by flashing below combination:
BL: A520FXXU2AQFA
AP+CP+CSC: All from Dec. 18 nougat build (QLA)
Click to expand...
Click to collapse
Can you upload BL that you used? It's work even you're in the latest security patch version december?
kobejor said:
Can you upload BL that you used? It's work even you're in the latest security patch version december?
Click to expand...
Click to collapse
I have attached the BL file. Yes, working on latest security patch (december).
waltermsalomon said:
I have attached the BL file. Yes, working on latest security patch (december).
Click to expand...
Click to collapse
Hey man it didn't work for me any other methods to root?
It did not work for me either. sw rev. check fail. device 3. binary 2
What country is your rom?
caiquess95 said:
It did not work for me either. sw rev. check fail. device 3. binary 2
What country is your rom?
Click to expand...
Click to collapse
It is Philippines (XTC) and phone origin is Vietnam, we are in the same CSC group and it should work. Please try exactly what I did.
Flash nougat BL with nov security patch along with the dec nougat build for AP+CP+CSC. After complete installation, I tried flashing TWRP (ofcourse enabling OEM unlock and USB debugging) and it failed. So went again to download mode then flashed BL (the file I attached) along with the dec nougat build. Again completed installation, then successfully flashed TWRP via odin. Afterwards, proceed to rooting my device.
waltermsalomon said:
It is Philippines (XTC) and phone origin is Vietnam, we are in the same CSC group and it should work. Please try exactly what I did.
Flash nougat BL with nov security patch along with the dec nougat build for AP+CP+CSC. After complete installation, I tried flashing TWRP (ofcourse enabling OEM unlock and USB debugging) and it failed. So went again to download mode then flashed BL (the file I attached) along with the dec nougat build. Again completed installation, then successfully flashed TWRP via odin. Afterwards, proceed to rooting my device.
Click to expand...
Click to collapse
I can not flash BL nougat from the September patch because it has level 2, and my BL is level 3 ....
Are you also Filipino?
Strange, maybe it is country specific issue. Mine has level 2 BL and rest Level 3 per dec build and I was successful flashing it. If you have a way to revert back from previous nougat build, say nov security patch, and can re-root your device, try flashing the latest nougat via flash fire. Use "flash firmware" action button and follow the instructions. Untick the "recovery" checkbox so you maintain twrp. From there, reroot your device through twrp. I also did this process and I was successful doing the whole thing.
kobejor said:
Are you also Filipino?
Click to expand...
Click to collapse
I am.
---------- Post added at 09:00 PM ---------- Previous post was at 08:25 PM ----------
caiquess95 said:
I can not flash BL nougat from the September patch because it has level 2, and my BL is level 3 ....
Click to expand...
Click to collapse
If you have flashed level 3 BL initially then you have a slim chance of downgrading your device from previous builds. Maybe I was just lucky enough because I used flashfire at first to upgrade to dec nougat build. I just didn't like settings menu as it was quite different from previous nougat, so I reflashed everything via odin but using level 2 BL and the rest level 3 (dec build). Try to follow the furom from the thread I initially gave you as they have also issues same as yours.
waltermsalomon said:
I am.
---------- Post added at 09:00 PM ---------- Previous post was at 08:25 PM ----------
If you have flashed level 3 BL initially then you have a slim chance of downgrading your device from previous builds. Maybe I was just lucky enough because I used flashfire at first to upgrade to dec nougat build. I just didn't like settings menu as it was quite different from previous nougat, so I reflashed everything via odin but using level 2 BL and the rest level 3 (dec build). Try to follow the furom from the thread I initially gave you as they have also issues same as yours.
Click to expand...
Click to collapse
then ... for me it will not be possible because my bl is level 3 ... no way I can flash a bl level 2
waltermsalomon said:
Strange, maybe it is country specific issue. Mine has level 2 BL and rest Level 3 per dec build and I was successful flashing it. If you have a way to revert back from previous nougat build, say nov security patch, and can re-root your device, try flashing the latest nougat via flash fire. Use "flash firmware" action button and follow the instructions. Untick the "recovery" checkbox so you maintain twrp. From there, reroot your device through twrp. I also did this process and I was successful doing the whole thing.
Click to expand...
Click to collapse
Flashfire doesn't flash bootloaders which is why you were able to root.
I hope there's a other way to install twrp or cwm even the boot loader can't downgrade.?
kobejor said:
I hope there's a other way to install twrp or cwm even the boot loader can't downgrade.?
Click to expand...
Click to collapse
Unlikely. Once it's locked that's usually it, no modifications possible.
It'll probably be locked down forever now unless Samsung release an unlocked firmware.
ashyx said:
Unlikely. Once it's locked that's usually it, no modifications possible.
It'll probably be locked down forever now unless Samsung release an unlocked firmware.
Click to expand...
Click to collapse
How sad to hear that!?
But I know a lot of great devs. here so it's possible to fix that :good:
ashyx said:
Flashfire doesn't flash bootloaders which is why you were able to root.
Click to expand...
Click to collapse
Oh, I was lucky didn't flash v3 BL even when I reflashed via odin. Thanks for that info.
Anyupdate about this problem?
Hi Folks!
Single thread for all the fastboot flashable stock firmwares and official OTAs.
Captured OREO 8.1.0 OTAs can be found in a separate folder, Check the region specific folders and DO READ THE DESCRIPTION OF THE FILES FOR MORE INFORMATION.
Make sure you are on unmodified stock rom with build number NPSS26.116-61-11(For RETIN Region OTA) and NPSS26.116-64-11(For RETBR Region OTA) before flashing/installing it, or else it wont flash/install.
Bootloader status does NOT matter, so unlocked guys can install it too, just make sure you have flashed stock first via fastboot.
Edit: Uploaded the fastboot flashable firmware OPS28.65-36.
Those who have unlocked bootloader can flash it via fastboot.
Locked bootloader ones can use the OTA files but make sure you are on eligible firmware.
Downloads:
Fastboot Flashable Firmwares: https://www.androidfilehost.com/?w=files&flid=214680
Captured OTAs: https://www.androidfilehost.com/?w=files&flid=282605
Suggestions:
Never re-lock your device's bootloader.
Never downgrade your firmware.
XDA:DevDB Information
Moto Stock Firmwares/Captured OREO OTAs, ROM for the Moto G5S Plus
Contributors
CheckYourScreen
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Created 2018-09-17
Last Updated 2018-09-22
Installation Steps
For OTA files:
Make sure you are on unmodified stock firmware, or just flash the stock rom again using fastboot.
Place the OTA file in internal storage(do not place it in a folder)
Go to settings>Apps and give storage permissions to Motorola Update Services app
Go to about and check for update.
Reserved
Wow.. ! thanks for this update. now my motorola will rock again !
Cant update bro my update app cant find package in internal storage i already gave permission app to storage
Nice updated..working fine here thank you
masnish kunwar said:
Cant update bro my update app cant find package in internal storage i already gave permission app to storage
Click to expand...
Click to collapse
Might sound weird, but if you're not on home network or wi-fi, it won't work.
AnubhavKumarc said:
Might sound weird, but if you're not on home network or wi-fi, it won't work.
Click to expand...
Click to collapse
No
Flash using sideload
Adi5 said:
No
Flash using sideload
Click to expand...
Click to collapse
It didn't detect the update on my phone when I was on roaming network, as soon as I switched to Wi-Fi it did, Motorola Update services doesn't work on roaming. And yeah it can be flashed using sideload, but that's not what I was talking about.
Can I update to oreo ota from soak test 1 which is on June 2018 patch.. I had Manually flashed the 1St soak at that time..
From this version, can I update to August 2018 oreo?
If yes, how?
Its soak test or stock rom ??
bakryu said:
Its soak test or stock rom ??
Click to expand...
Click to collapse
Looks like soak, by seeing the kernel version "prerelease"
geekychandu said:
Looks like soak, by seeing the kernel version "prerelease"
Click to expand...
Click to collapse
No
Rajat22 said:
Nice updated..working fine here thank you
Click to expand...
Click to collapse
I wonder if it's final OTA, then why the kernel version says "prerelease"
Can't set wallpaper in this rom...
---------- Post added at 06:40 PM ---------- Previous post was at 06:09 PM ----------
hazan95 said:
Can't set wallpaper in this rom...
Click to expand...
Click to collapse
Don't worry figured it Out!
Pls provide mirror links AndroidFileHost is slow AF.
After I flashed Oreo update my network lost bro what should i do?? i tried to restore it with efs and presist but not worked..
What about reteu channel? It was not mentioned at all
bakryu said:
Its soak test or stock rom ??
Click to expand...
Click to collapse
Final stable build of stock oreo.
geekychandu said:
Looks like soak, by seeing the kernel version "prerelease"
Click to expand...
Click to collapse
geekychandu said:
I wonder if it's final OTA, then why the kernel version says "prerelease"
Click to expand...
Click to collapse
Thats GCC toolchain release info for god sake
dheerajz said:
Pls provide mirror links AndroidFileHost is slow AF.
Click to expand...
Click to collapse
You can wait for moto to send you ota. No mirrors plz.
masnish kunwar said:
After I flashed Oreo update my network lost bro what should i do?? i tried to restore it with efs and presist but not worked..
Click to expand...
Click to collapse
Follow the volte fix. Join telegram group (https://t.me/g5splus) and type #voltefix and follow the steps.
eCoB said:
What about reteu channel? It was not mentioned at all
Click to expand...
Click to collapse
Official roll out and ota packages have been released only for retbr and retin region. Wait for moto to release ota for EU region, I'll upload it once available.