Related
So, I have a 32gb Amazon-variant XT1625 on MPJ24.139-48 with an unlocked bootloader and root. I want to update to Nougat, but it's looking like setting up to take the Amazon update is going to be a fair amount of effort; I'm wondering if it's possible to just flash the retail version of Nougat since it's looking like I'm going to have to go to a fair sum of effort anyway.
I've also heard that Moto G4 Plus ROMs will work on the G4, but I don't know the specifics on that.
i dont see why not as long as you already unlocked the bootloader prior to Moto(Lenovo) disallowed unlocking of amazon varients of the g4. heres a link to the stock nougat firmware
https://androidfilehost.com/?fid=673368273298955218
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Travisholt92 said:
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Click to expand...
Click to collapse
then you was able to flash retail version in a amazon prime phone? I have one and it dont boot if i instal a retail version.
di anybody actually get this working? I had the same issue as @iurd2007 I was able to unlock the bootloader just fine. The flash appeared to have taken successfully. But it just gets caught in a boot loop when trying to reboot the system after the flash. I followed the instructions here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
okay, so i've tried various roms both official and unofficial, as well as even the stock Nougat and Oreo flashable roms found here:
https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367
So far, the only ROM i've been able to get installed is omni rom 9, but it keeps crashing several apps over and over on the setup wizard. I've read somewhere that using a different version of TWRP recovery image might help. I've tried the official TWRP recovery from twrp.me, the patched arm64 version found here: https://sourceforge.net/projects/tw...3-r1-athene-arm64_rajatgupta1998.img/download , also the latest version patched for efs backup/restore here: https://forum.xda-developers.com/devdb/project/?id=29106#downloads. So far the the one that seems to work the best is the third version of TWRP. It would be nice if all these custom patches made it back into an official release, but it's probably asking a lot of a phone that is almost 4 years old at this point. and a budget friendly phone at that.
Hey there !
I have a Moto G5 Plus International edition (XT1681) with firmware NPNS25.137-92-4 (latest January Patch).
I want to know what firmware to download from here (https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/) for factory flash not to get bricked like an idiot.
I don't know which one is good
Thanks
The last 2 ROMs are for your device, if you have a custom recovery I recommend to install the flashable version from this link .
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Here are the same version of your device NPNS25.137-92-4 (20180101 security patch)
Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/
CobraBoyFR said:
Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/
Click to expand...
Click to collapse
i didnt try to flash over a fastboot rom, maybe you cant do that.
Thanks
But basically, what I need is flashing full stock firmware (with recovery and kernel), no matter if it's january update or not. Just the factory images I had when I bought the phone. And I don't know what version is OK for my phone (XT1681 with NPNS25.137-92-4 now) 'cause I don't want to hard brick it when OTA updating (to Oreo for example)
From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.
RokCruz said:
From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.
Click to expand...
Click to collapse
Right now I'm on stock NPNS25.137-92-4, with TWRP recovery + Magisk root + ElementalX kernel
I'm not planning to flash any custom ROM for the moment. When the official Oreo update comes out, I want to update. But I know it won't go well if I OTA update it with my current configuration. That's why I want to be able to flash stock with fastboot (rough clean install), no matter what version I get : All i want is to be able to update to Oreo when it's out. Problem is, I don't know which image I need to download from here : https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I know it's there, but don't know exactly the good version.
This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.
RokCruz said:
This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.
Click to expand...
Click to collapse
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.
echo92 said:
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.
Click to expand...
Click to collapse
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?
RokCruz said:
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?
Click to expand...
Click to collapse
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
That was roughly what I figured out but damn, those explanations, thanks buddy :highfive:
The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.
driverdis said:
The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.
Click to expand...
Click to collapse
On xt1681 right?
Thanks for your feedback
echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
yeah i cant apply normal OTA over flashable rom. I was on NPN25.137-92(flashable) i download NPNS25.137-92-4(flashable too) i dirty flashed it and it works perfect without lose my stuff
I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.
jkl555 said:
I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.
Click to expand...
Click to collapse
Just to reply to myself for (2). I found the following link
https://www.stockrom.net/2017/05/st...g5-plus-xt1683-xt1681-android-7-0-nougat.html
Hey there devs and V20 users alike.
As if there wasn't already hesitation enough to root this headache of a phone, and just when I was about ready to take the dive, I received the Oreo OTA update about three weeks ago.
Since updating, I've been enjoying the phone thoroughly.
If I'm going to be honest, this is the first phone I've owned (out of MANY since the Galaxy Captivate S days) that I have been satisfied using without root. It's an absolute multimedia powerhouse. However, little things like the inability to utilize ad blockers, tweak kernels, access root storage, etc. Does bother me now and then, although infrequently.
I'm looking through the forum here, and I'm beginning to think that due to LG's unbelievably long release of oereo, and the difficulty of root, devs have long left this device in the dust.
Unless I'm missing something, is there any rooted Oreo ROM available ATM? I absolutely will not revert to 7.1 again.
Thanks in advance!
Murph.
murph187 said:
Hey there devs and V20 users alike.
As if there wasn't already hesitation enough to root this headache of a phone, and just when I was about ready to take the dive, I received the Oreo OTA update about three weeks ago.
Since updating, I've been enjoying the phone thoroughly. If I'm going to be honest, this is the first phone I've owned (out of MANY since the Galaxy Captivate S days, that I have been satisfied using without root. It's an absolute multimedia powerhouse. However, little things like the inability to utilize ad blockers, tweak kernels, access root storage, etc. Does bother me now and then, although infrequently.
I'm looking through the forum here, and I'm beginning to think that due to LG's unbelievably long release of oereo, and the difficulty of root, devs have long left this device in the dust.
Unless I'm missing something, is there any rooted Oreo ROM available ATM? I absolutely will not revert to 7.1 again.
Thanks in advance!
Murph.
Click to expand...
Click to collapse
No root yet. we still have a handful of devs around although it is slowly becoming more of a ghost town as far as Dev work.
Oreo hasn't even been released for most variants yet. Just chill out and wait.
Phoenix591 said:
Oreo hasn't even been released for most variants yet. Just chill out and wait.
Click to expand...
Click to collapse
Relax slim, it's just a question.
Phoenix591 said:
Oreo hasn't even been released for most variants yet. Just chill out and wait.
Click to expand...
Click to collapse
^^^
I can confirm the ls997 has oreo. and i've seen a few other people talking about their oreo updates here on XDA on different models.. Idk how many models there are of the v20 though..... Still waiting for ls997 root I'd love to OC this phone for even better performance Or at least manage its cpu to avoid overheating 24/7
texas7412 said:
^^^
I can confirm the ls997 has oreo. and i've seen a few other people talking about their oreo updates here on XDA on different models.. Idk how many models there are of the v20 though..... Still waiting for ls997 root I'd love to OC this phone for even better performance Or at least manage its cpu to avoid overheating 24/7
Click to expand...
Click to collapse
Have Oreo: F800 LS997 H915 H910
Not yet: H910PR H918 H990{N,DS several regions getting otas at different times within those variants} US996(BPT USC USA) VS995
Phoenix591 said:
Have Oreo: F800 LS997 H915 H910
Not yet: H910PR H918 H990{N,DS several regions getting otas at different times within those variants} US996(BPT USC USA) VS995
Click to expand...
Click to collapse
VS995 already got the update 1 or 2 days ago, still it is too late already
root please
please dev, find a way to root my LG V20 F800S Korean version, Oreo. :crying:
In order to get root with Oreo on any model besides the H918, a custom kernel will be needed -- and I don't mean just compiling up the sources from LG.
I am going to try and migrate from my H910 over to one of my H918s .. but that is going to take a bit. Then I will have a phone that can use the eng. bootloader, and can actually start to work on it.
-- Brian
runningnak3d said:
In order to get root with Oreo on any model besides the H918, a custom kernel will be needed -- and I don't mean just compiling up the sources from LG.
I am going to try and migrate from my H910 over to one of my H918s .. but that is going to take a bit. Then I will have a phone that can use the eng. bootloader, and can actually start to work on it.
-- Brian
Click to expand...
Click to collapse
Hey Brian, glad to see you still around these parts lol
Edit
I thought the key to root on oreo with eng bootloader was the 996 oreo release or has that changed?
Sent from my LG-H910 using XDA Labs
Yea, I am definitely still around -- just nothing I can do right now.
I am pretty sure I can get it working with a modified kernel, but I need to be able to see logs -- so that means I need my H910
-- Brian
runningnak3d said:
Yea, I am definitely still around -- just nothing I can do right now.
I am pretty sure I can get it working with a modified kernel, but I need to be able to see logs -- so that means I need my H910
-- Brian
Click to expand...
Click to collapse
hi brian,
if there's something i can help you or if you need something to do with rooting lg v20 oreo, just let me know. i really want to root my F800S
Dirtysanta eng aboot works on oreo now
runningnak3d said:
In order to get root with Oreo on any model besides the H918, a custom kernel will be needed -- and I don't mean just compiling up the sources from LG.
I am going to try and migrate from my H910 over to one of my H918s .. but that is going to take a bit. Then I will have a phone that can use the eng. bootloader, and can actually start to work on it.
-- Brian
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/h910-att-lg-v20-stock-oreo-rooted-t3846384
Recently they have found out that to get eng aboot to work with oreo firmware, it was just a simple zip making modifying 2 files.
1. stock aboot changed to common dirtysanta eng aboot
2. stock v20 variant oreo boot changed to magisk patched stock oreo v20 variant boot
We have to keep the recovery as stock recovery so letting the previous twrp get flashed over.
The key is letting the oreo firmware boot up first time with stock recovery and then data will work like normal
Then we boot it up first time and it will get to system and then do quick setup and then go into fastboot (thanks to the eng aboot intact) to push the twrp recovery back to working order again.
So it was just simply doing that instead of using patchd lg up to partition dl to ignore the 3 things : aboot, boot, recovery.
That means eng aboot is still good to be able to use on oreo for all dirtysanta v20s .
I am personally running h910 oreo root with very early build of mk2000 beta 2 oreo kernel. My phone gets full lte data like normal. The battery drain is much improved from nougat while still having the same kind of performance I was used to on rooted nougat.
Asked this on other threads but no answers yet, let me see if I get my answers here
I have a f800l lg v20 not Rooted
Android 7.0
Updated security patch 1st september 2016
Kernel 3.18.31
Build no Nrd90m
Software version F800L 10g
My question is that can I update my Android to Oreo 8.0 which is available via Software update and then gain root access? If no, what is the last update limit for me to not lose rooting possibility. Or is it possible to downgrade to a previous update state after updating it to either Oreo 8.0 or other updated security patch levels? What would you suggest? I've heard Oreo is good with little battery drainage percentage as compared to Nougat which is my primary interest. I don't want to make a move to lose my rooting ability. Are there any other means available to upgrade to oreo without using lg software update in order to achieve both Oreo and root? And if it is not possible to achieve both Oreo and root are there any custom roms or kernels available with good battery drainage percentage? What would suit me the best. Sorry in advance for asking so many questions and not knowing if these questions have already been discussed and answered.
Thank you
Your phone is still ARB 0, so you can do whatever you want.
As for rooting Oreo, now that I know that it expects stock recovery on first boot, I will be posting zips for every model that has a KDZ.
You will need to root your phone first. Since you are on September 2016 patch, use DirtySanta.
-- Brian
runningnak3d said:
Your phone is still ARB 0, so you can do whatever you want.
As for rooting Oreo, now that I know that it expects stock recovery on first boot, I will be posting zips for every model that has a KDZ.
You will need to root your phone first. Since you are on September 2016 patch, use DirtySanta.
-- Brian
Click to expand...
Click to collapse
by the way, no point in making the zip for h915 oreo.
I have tried with the same new method zip that was made with the 2 modified files + stock recovery.
The h915 modem just doesn't want to work with eng aboot whatsoever just like how it was on h915 nougat rooted.
please post oreo zip file for F800L, i can't wait to have oreo rooted on my F800L
darkknight200 said:
by the way, no point in making the zip for h915 oreo.
I have tried with the same new method zip that was made with the 2 modified files + stock recovery.
The h915 modem just doesn't want to work with eng aboot whatsoever just like how it was on h915 nougat rooted.
Click to expand...
Click to collapse
Perhaps this is something that can be circumvented in the kernel, like runningnak3d was talking about earlier, and like emdroidle did for H990.
I don't know how it works, but I could try enabling the same fix that's used for h990, for h915 oreo.
thank you runningnak3d
Ok I'll llet you know once I root my F800 L
Update: I managed to flash twrp via DirtySanta method. I can get into recovery twrp and use it but i haven't flashed SuperSu yet. I can't get comfort view working and the battery is draining relatively fast, So by flashing super su will I get Comfort view and old battery drainage rate back or do I have to do something else? Shall I flash supersu? I get a red triangle mark every time I restart my phone which takes longer than it used to in order to boot, which means I have Bootloader unlocked, can unlocking bootloader ignite problems like long booting duration, inability to use comfort view and fast battery drainage? What do you suggest I do? flash supersu? or relock the boot loader without getting Supersu? Will doing so even fix these problems becasue I planned on rooting to get better battery drainage percentage, instead I get more battery drainage, please help @[runningnak3d]
Hello!
I have a rooted LG V20 H990DS running nougat. Can I upgrade to Oreo without loosing root?
If yes, could you please tell me what is the best way to do so?
Phone: LG V20 H990DS
kernel: 3.18.90-DOTS_H990_kernel-leicxan_jahlex-v1.4
ROM: stock
Build Number: NRD90M
OS Version: Nougat (7.0)
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Thanks for the response
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
psychopac said:
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Click to expand...
Click to collapse
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
kash664 said:
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
Click to expand...
Click to collapse
Make sure to follow the flashing instructions mentioned by the thread OP properly
psychopac said:
Make sure to follow the flashing instructions mentioned by the thread OP properly
Click to expand...
Click to collapse
Yes. Hope everything turns out fine
kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
I hope i can help !!
vishalrickz said:
I hope i can help !!
Click to expand...
Click to collapse
Sure sir
I have an H918 that is running 10i and is still ARB 0.
I am researching the various root methods and I am wondering if there is any real benefit to staying on ARB 0.
If there is, I'll go with DirtyCow, if not, I can go with Lafsploit.
If I use Lafsploit and flash 10p, and increment to ARB 1, will this come back to bite me in any way?
I don't think I'll want to stay on 10i or roll back to this version. I think I will probably stay on 10u or some Oreo variant.
I would appreciate any input on this.