If you want to sell it, then these builds are not suitable (as you cannot lock the bootloader). You would want to use the fastboot roms instead. Search the forums.
[Oreo][Stock][Rom] TWRP Flashable Stock Builds
- Thread starter NZedPred
- Start date
Not sure, but I think you have to flash a stock Rom via ADB and then relock the bootloader. After that update via OTA to the most recent version.
May be someone can give you more details and links how to do it properly.
Hi,
I flashed one of these builds with TWRP some time ago and it has always rebooted into TWRP instead of just rebooting into Android, this was fine with me, I just booted into bootloader and then clicked Start.
Now I want to give the phone to someone who will not be able to do this (my mother in law, not great with technology) so can I ask:
1. Is there a way to get it to reboot normally as it is, with TWRP and rooted?
or
2. How can I easily set it back completely to a stock Oreo/recovery? (one from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/), can you flash these through TWRP or need to use the ADB method?
There are so many threads I am not sure which one to follow! I will not be backing up anything so if it gets completely wiped it's fine, and I don't need to relock.
Looks like me and HazeMC want to do similar things
I flashed one of these builds with TWRP some time ago and it has always rebooted into TWRP instead of just rebooting into Android, this was fine with me, I just booted into bootloader and then clicked Start.
Now I want to give the phone to someone who will not be able to do this (my mother in law, not great with technology) so can I ask:
1. Is there a way to get it to reboot normally as it is, with TWRP and rooted?
or
2. How can I easily set it back completely to a stock Oreo/recovery? (one from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/), can you flash these through TWRP or need to use the ADB method?
There are so many threads I am not sure which one to follow! I will not be backing up anything so if it gets completely wiped it's fine, and I don't need to relock.
Looks like me and HazeMC want to do similar things
February 2019 security patch release out - OPSS28.85-17-6
New build available now with the February security patches. This is from the retus software channel, but as always, we're pretty safe if we're on other regions too.
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-aroma.zip
Dropbox - potter-twrp-flashable-OPSS28.85-17-6-aroma.zip
In case some of you have missed it, I had finally worked out what the underlying issue is regarding the touchscreen not working after flashing one of these Oreo builds. Head over to post #3 for the full details.
Happy flashing, and hit thanks if you appreciate my work!
New build available now with the February security patches. This is from the retus software channel, but as always, we're pretty safe if we're on other regions too.
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-aroma.zip
Dropbox - potter-twrp-flashable-OPSS28.85-17-6-aroma.zip
In case some of you have missed it, I had finally worked out what the underlying issue is regarding the touchscreen not working after flashing one of these Oreo builds. Head over to post #3 for the full details.
Happy flashing, and hit thanks if you appreciate my work!
I do not have the fastboot zip for this update, it has been built using the OTA.
So after installing OPSS28.85-17-6 I had the issue below and followed the steps from earlier in the post:
On soak test 2 or later, I have my IMEI but no signal. What can I do?
In all cases where this has happened, the user's phone has relied upon an EFS backup for IMEI, due to flashing another persist. In these cases, it appears that the only way to get a signal is to use the firmware (i.e. modem, fsg, dsp - refer previous FAQ) from soak test 1. We're probably seeing here that the EFS does in fact need to be recreated to be valid. Unfortunately for these users, by not having their own persist, they are stuck with an old EFS and the newer firmwares appear to not work.
To do this
if you are already on Soak Test 2 or later, download the Soak Test 1 firmware download at either of these links:
Android File Host - oreo-soak1-firmware.zip
Dropbox - oreo-soak1-firmware.zip
If you are on Soak Test 1, install Soak Test 2 or later / official aroma installer and de-select firmware
Everything seems to be working OK at this point but will I be able to install future updates? How will this affect me going forward? Also, if I just want to go back to completely stock with OTA updates can I do that?
On soak test 2 or later, I have my IMEI but no signal. What can I do?
In all cases where this has happened, the user's phone has relied upon an EFS backup for IMEI, due to flashing another persist. In these cases, it appears that the only way to get a signal is to use the firmware (i.e. modem, fsg, dsp - refer previous FAQ) from soak test 1. We're probably seeing here that the EFS does in fact need to be recreated to be valid. Unfortunately for these users, by not having their own persist, they are stuck with an old EFS and the newer firmwares appear to not work.
To do this
if you are already on Soak Test 2 or later, download the Soak Test 1 firmware download at either of these links:
Android File Host - oreo-soak1-firmware.zip
Dropbox - oreo-soak1-firmware.zip
If you are on Soak Test 1, install Soak Test 2 or later / official aroma installer and de-select firmware
Everything seems to be working OK at this point but will I be able to install future updates? How will this affect me going forward? Also, if I just want to go back to completely stock with OTA updates can I do that?
You won't be able to go back to full stock unfortunately. Any future updates (if any) will still require Soak test 1 firmware.
Yes you can install it on retail potter. (Hope i got the question right...). I'm with a potter retail gb.
That really sucks... if I would have known about this potential problem I wouldn't have moved to Oreo. The only builds that have been installed on this phone were the [Nougat][Stock][Rom] TWRP Flashable Stock Builds. Any idea what happened here? I used the persist / modem backup function from this Oreo installer, is it possible to go back to Nougat if I wanted to?
Last edited:
Were you ever on a custom rom? Most people who have had issues of this sort were on custom ROMs. The stock builds shouldn't have caused you any problems. Only other possibility is an app with root access has caused the problem.
You can go back to most using the TWRP flashable nougat builds.
I was never on any custom roms, only the Nougat builds mentioned previously . I did have xposed framework installed but only used ad away and boot manager. Also had rom manager installed but that was because I purchased it previously on a different phone and installed it but never used it on this phone. I really don't use many apps. I wish I had went back to stock and had OTA updates. I hate the update notification that I had to deal with on the Nougat TWRP build, but now opening apps is actually slower with Oreo than it was with Nougat. Seems like my phone is slower in general.
I just got an update notification ... looks like i actually flashed a zip I had downloaded earlier in the month, OPS28.85-17-4-aroma.zip rather than -6..... So I need to flash -6 and then reflash the soak1 firmware again I guess?
Last edited:
You can install the latest build, and just deselect the firmware option. That will keep whatever firmware you have currently, in your case soak test 1.I was never on any custom roms, only the Nougat builds mentioned previously . I did have xposed framework installed but only used ad away and boot manager. Also had rom manager installed but that was because I purchased it previously on a different phone and installed it but never used it on this phone. I really don't use many apps. I wish I had went back to stock and had OTA updates. I hate the update notification that I had to deal with on the Nougat TWRP build, but now opening apps is actually slower with Oreo than it was with Nougat. Seems like my phone is slower in general.
I just got an update notification ... looks like i actually flashed a zip I had downloaded earlier in the month, OPS28.85-17-4-aroma.zip rather than -6..... So I need to flash -6 and then reflash the soak1 firmware again I guess?
Also, if you don't mind, can you send me a private message with a link to the backup of your persist that the aroma installer made? I'd be interested in seeing if there is a particular issue with yours. You can refer to my pinned thread on fixing persist in the guides Forum for more info there.
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Sent you the message. Flashed the newest build with firmware unchecked and even with the soak 1 firmware I have no signal bar now. It says Sim not allowed MM3. I'll try flashing the build with the newest firmware. Am I supposed to enable the erase EFS?
UPDATE: Flashed the latest build including the firmware and everything appears good to go now, I have signal again.... wtf?
Last edited:
Could it have been an issue with the sim card, or your network provider? In any case, if it is working with the latest firmware, then you probably don't have an issue with your persist.
It is indeed working fine now. I don't know if it could have been the sim or provider but I doubt it. Here's the chain of events:
I was on the TWRP flashable stock Nougat latest build. I clean flashed the 2nd newest Oreo build (I meant to flash the newest) and backed up modem/persist with the aroma installer, (not sure if I erased EFS but I did the full backup in the installer) and flashed magisk. After booting I had no cell signal. Flashed the Soak1 firmware and got a signal. I used it for 4-5 days or so with no problems that I observed other than just generally being less snappy that Nougat. Today I flashed the latest Oreo build without erasing EFS or installing firmware and after restart I had no signal again. I flashed the latest build again with EFS unselected but installed the firmware and everything is now OK. Weird wild stuff.
Last edited:
is it the official oreo 8.1 in a flashable zip, or build over the stock oreo firmware
I originally updated to official oreo 8.1, which i have uninstalled and due to a failed attempt in installing custom rom, i wish to rollback to stock oreo firmware.
If i flash the aforementioned oreo firmware (non aroma version), will it pose an issue with my system? mentioned in the notes was loss of efs and /persist directory. Will it hamper with the described data, partitions? if so, what is the best way to get around this issue? my device has obviously the bootloader unlocked as well as twrp recovery installed via which i'm able to access system and also external sd card and otg thumb drive.
any help will be appreciated.
I originally updated to official oreo 8.1, which i have uninstalled and due to a failed attempt in installing custom rom, i wish to rollback to stock oreo firmware.
If i flash the aforementioned oreo firmware (non aroma version), will it pose an issue with my system? mentioned in the notes was loss of efs and /persist directory. Will it hamper with the described data, partitions? if so, what is the best way to get around this issue? my device has obviously the bootloader unlocked as well as twrp recovery installed via which i'm able to access system and also external sd card and otg thumb drive.
any help will be appreciated.
Last edited:
Any idea why the latest Xposed framework would cause a boot loop with this build?
The bit underlined was the problem. You cannot use the Oreo firmware on Nougat.
Nope, and not something that I or any other Rom developer would look into. Xposed questions should go into an Xposed thread.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone