Database Info

Has anyone tried using latest flashfire to upgrade NOF26V?

will this keep the phone rooted like it does ever.
to flash the full image and root again is not very easy for me

It seems that no one is gonna take a try, I will and revert.

Just finished upgrading via flash fire. It worked

What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?

V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.
Tarp was removed, now no recovery available
sliding_billy said:
What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?
Click to expand...
Click to collapse

bush911 said:
V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.
Tarp was removed, now no recovery available
Click to expand...
Click to collapse
Thanks for investigating. I would have thought you would flash the OTA. Doesn't seem to improve the process if recovery is removed but root isn't.

I did. Didn't work. Downloaded OTA. Flashfire kicked in (I'm using FlashFire Pro v0.55.1). It appeared to process the OTA. I flashed. OTA was not successful. I re-flashed SuperSU to restore root.

Flashfire works great
I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.

I just retook the 7.1.2 OTA but did not restart after download. Opened FlashFire it autodetected the OTA, offered to install and I accepted. Everything went fine. Still have Su and on Sharkey kernal

josephpalozzi said:
I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.
Click to expand...
Click to collapse
I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?
edit: I was able to update to the Feb security patch, but lost twrp in the process. I tried the steps above again, this time I was presented with the ota available pop up screen which I didnt get the first time around. Even with the "preserve recovery" option ticked, it didnt preserve it. I get "no command" when I try to boot into recovery.

Just used TWRP sideload, TWRP IMG, TWRP install and SuperSU install to update XL to February. About to do Pixel. I've got FashFire installed and waiting until it is working in a more stable fashion. No point in fixing what ain't broke for me right now.

llong31 said:
I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?
Click to expand...
Click to collapse
There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today

mac796 said:
There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today
Click to expand...
Click to collapse
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.

llong31 said:
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system
Click to expand...
Click to collapse

mac796 said:
llong31 said:
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system
Click to expand...
Click to collapse
I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.
Click to expand...
Click to collapse

llong31 said:
mac796 said:
I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.
Click to expand...
Click to collapse
Maybe I'll try the auto detect see if that helps, in not sure if L speed does. I think most stuff for pixel is systemless
Click to expand...
Click to collapse

Sorry to bump this old thread...how long were ya'll phones 'black' during Flashfire? Mine has been black (but still connected to storage via PC so it's not dead) for like 25 min.
EDIT: After almost an hour, I gave up. I force rebooted the phone hoping Flashfire didn't do anything and it looks like it didn't. Phone booted fine. Going to use the old method and sideload the OTA.

I've used the OTA file from the typical update with FlashFire the past couple months, and I used a file downloaded from Google once before (I don't remember if it was on the phone or a flash drive). The screen didn't stay black very long the times I've used it, I'd guess less than a minute, so apparently something didn't work correctly. Looking through the app and documentation, I'm not sure what you meant by "still connected to storage via PC".

Oxygen OS 5.1.11

Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
System
1.Optimized network connection
2.Optimized stability for wi-fi connection
3.Fixed screen flickering issue in day light
4.General bug fixes and improvements
5.confirm pin without tapping
Camera
Improved HDR mode

Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.

I also get that update.
If i download it.. can i just not update right away?
because i want to manually update from twrp and re root with magisk.
Thanks in advance
Sent from my ONEPLUS A6000 using Tapatalk

ossy1337 said:
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
Click to expand...
Click to collapse
I have no photos with older firmware.i think now the photos taken are more brighter

Root users beware: issues with newer TWRP version!
This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.

So since twrp latest works fine on my device with encryption included, I can just start the update?
Sent from my ONEPLUS A6003 using Tapatalk

Neurom67 said:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
Click to expand...
Click to collapse
Can you link 3.2.1-1 version? https://eu.dl.twrp.me/enchilada/ There is only 3.2.1-0 or 3.2.2-0

I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails

No problem with blue twrp.

nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Fails for everyone atm. Was working fine for me until two days ago before Google updated the api
Sent from my ONEPLUS A6003 using Tapatalk

nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Here is why; https://mobile.twitter.com/topjohnwu/status/1029239685338419200

3.2.1.0 installed 5.1.11 fine on my OP6.

nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
SpectraFun said:
No problem with blue twrp.
Click to expand...
Click to collapse
Batfink33 said:
3.2.1.0 installed 5.1.11 fine on my OP6.
Click to expand...
Click to collapse
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?

Have TWRP 3.2.3 and installed 5.1.11 just fine.

SMS786 said:
Have TWRP 3.2.3 and installed 5.1.11 just fine.
Click to expand...
Click to collapse
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk

Vuska said:
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Didn't disable my pattern lock..worked just fine.
I downloaded the zip online and installed through TWRP. Just make sure to reinstall your TWRP installer after installing the full rom OTA (wipe cache/dalvik first), then reboot back into TWRP and install Magisk..then boot into system.

The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade

Chinaroad said:
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Click to expand...
Click to collapse
People seem to be saying this for every release

giebeka said:
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Click to expand...
Click to collapse
Used Oxygen updater to download zip. Rebooted to bootloader. Went Install and selected ZIP. then added TWRP zip as well. Installed both. Rebooted to bootloader again. Flashed elementalx kernel(you can skip it) and magisk. All works fine.

kakkooran said:
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
...
5.confirm pin without tapping
Click to expand...
Click to collapse
I can't find where to enable this. Anyone found it?

[ROOT] and [Solve] every issue in oxgyen os open beta {1/2/3} (Android pie 9.0)

I've managed to solve all problem by rooting and installing magisk
1. Some apps may not work properly
I have tried every app I used in oreo and each app works fine (I know this is not a solution )
2. Google pay not works
Solution-Google pay works by using a magisk module called
*tezhider4magisk*
https://androidfilehost.com/?fid=5862345805528042557
3. Google play shows device not certified
Solution - Google play shows device is certified using magisk module called
*ClearPlayStoreWithServiesData4Magisk*
https://androidfilehost.com/?fid=890278863836289937
4. Safety net not passed in magisk on open beta 1/2/3
Solution - for safety net to pass in magisk we need to edit a line in build.prop (have to some file explore like es file explorer or root explorer to edit build.prop)
Replace
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:9/PKQ1.180716.001/1808301430:user/release-keys
Click to expand...
Click to collapse
With
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Click to expand...
Click to collapse
5. For rooting oxgyen os open beta 1/2/3
Follow guide from developer [Manikandanguru] (all thanks to him?)
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853

Is there a fix yet for aod/ambient display yet?

Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/

For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.

sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Doesn't work, crashes display settings.

sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?

Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
For me aod/ambient display works perfectly
Have you dirty flashed new beta
Try doing a factory reset I hope that will fix it

BossNexusS said:
For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.
Click to expand...
Click to collapse
Try clearing cache from recovery that solves a lot of issues

Gmos24 said:
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?
Click to expand...
Click to collapse
Woah! Sorry about that, I guess I should have tested it first on P. I'll flash OOS Open Beta 2 today and then try this mod. Will update if it works.
And status bar issue is a strange one, no idea about that!

Can we get incremental ota update even when unlocked and magisk installed (no twrp)?

I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now

droid-devz,
Flash Oos ob02, then twrp blu spark.
Reboot to twrp to check if it's working. Flash Magisk 17.1.
Reboot to system.

Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Yess i just updated from beta 1 to beta 2 no problem
You'll just lose root everytime you update and have to install just magisk again
Don't install custom recovery that causes problems I guess use the above method (in the thread)

droid-devz said:
I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now
Click to expand...
Click to collapse
Official twrp doesn't work only blue star twrp works

Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Probably not..magisk root rewrites the boot image..safest bet would be to use update manager to flash whole rom updates, then reinstall magisk.

CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?

JRevenge said:
CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?
Click to expand...
Click to collapse
does not happen with me !!!

Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?

digidude512 said:
Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?
Click to expand...
Click to collapse
safety net passes with current canary build of magisk
plug this into the custom section in the magisk settings under update channel: https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json

sorry, hit send before it finished uploading

[H910][Oreo][Stock][Rooted] AT&T LG V20 Stock Oreo rooted flashable zip

Good Morning
New: Well AT&T updated us to Sept Security patch
here's the new Stock rooted rom > H910_20h_Oreo_full_rooted.zip > https://www.androidfilehost.com/?fid=1322778262904015326
Tested by @darkknight200
i dirty flashed over the 20g rooted setup. It booted up fine and works like normal.
Now have to debloat att apps and restore twrp. This time i used twrp app to restore twrp right in system and it worked properly. Saves the hassle to go into fastboot to push twrp.
All in all those are minor inconveniences, The zip is fine.
Thanks allot man.
Click to expand...
Click to collapse
After @NotYetADev posted his VS995 rooted Oreo We decided to give it a try on the H910.
It's not perfect but it does work. You'll need to Format Data and flash the H910_20g_Oreo_full_rooted.zip + the Newest - H910_mk2000 kernel from recovery-twrp-h910-2018-10-18.img
Your phone will be wiped and updated to Stock rooted Oreo so backup your phone first!
If you have never rooted your H910 you'll need to use the guide here first > https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Note: when you get where you would flash 10r just use my rom instead. Don't forget to flash the kernel after the rom
Note2: Flash TWRP again before you reboot (Install / Install Image / recovery-twrp-h910-2018-10-18.img to Recovery
It's also recommended to use the new TWRP for Oreo found here > https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Note: you'll have to flash TWRP back to the phone after flashing the rom and kernel because it installs stock recovery.
If you have any problems getting DATA on any sim other than AT&T check this post to fix your APN > https://forum.xda-developers.com/showpost.php?p=79619740&postcount=244
Thanks @StrikerTheHedgefox
After your phone is setup be sure and install the Magisk apk
Hide unlocked Bootloader warning boot screen by 4shared < This removes the ugly pink and black screen on reboot. I tested it and it works great
Huge thanks go to @darkknight200 and @askermk2000 for the Idea and the kernel.

thank u. but does the fingerprint work and what are the bugs if any

Yes fingerprint scanner works
Side note you'll have to flash twrp again
Use this version > https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239 and you should have no problems
aminjomaa13 said:
thank u. but does the fingerprint work and what are the bugs if any
Click to expand...
Click to collapse
Sent from my PH-1 using Tapatalk

if i have root then cant i just use flashr or another flashing app for twrp

aminjomaa13 said:
if i have root then cant i just use flashr or another flashing app for twrp
Click to expand...
Click to collapse
I installing twrp img from twrp just after flashing the ROM would do the trick.

if i dont have an at&t sim card ，will this rooted rom restrict some function such as wifispot 。。。。。。

Test flashed this on my h915 device. I have working full data and root and everything works.
Just gotta debloat it myself
running very smooth

zkm15 said:
if i dont have an at&t sim card ，will this rooted rom restrict some function such as wifispot 。。。。。。
Click to expand...
Click to collapse
Its the Stock Oreo rom dump .. only thing changed is a patched_boot.img and the Eng_aboot.img
in fact the original files are in the rom too they just don't get flashed
everything should work as expected

battery life took a hit what are the optimal CPU GPU values to optimize battery without totally crushing performance

anyone else pass both safetynet test on magisk 17.2 on h910 oreo?
It seems to be failing most of the time for me.

aminjomaa13 said:
battery life took a hit what are the optimal CPU GPU values to optimize battery without totally crushing performance
Click to expand...
Click to collapse
this question is better left in the Kernel thread > https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
I never mess with kernel setting aside from the Screen settings

darkknight200 said:
anyone else pass both safetynet test on magisk 17.2 on h910 oreo?
It seems to be failing most of the time for me.
Click to expand...
Click to collapse
safetynet test for non at&t sim card ？ it is a problem on android N .

Awesome! Glad this works on other devices! Good job, XDA!

NotYetADev said:
Awesome! Glad this works on other devices! Good job, XDA!
Click to expand...
Click to collapse
ya the zip method you did with modifying only 2 files in the whole firmware should work on all other dirtysanta devices.
Edit:
i re-flashed the h910 oreo and setup and debloated everything again. Now I am passing safetynet with no problems and certified device. very weird.
One thing to note, this is on the early build of Oreo TWRP that I was able to flash properly vs using nouget twrp the first 2 flashes that gave me bugs each time.

darkknight200 said:
ya the zip method you did with modifying only 2 files in the whole firmware should work on all other dirtysanta devices.
Edit:
i re-flashed the h910 oreo and setup and debloated everything again. Now I am passing safetynet with no problems and certified device. very weird.
One thing to note, this is on the early build of Oreo TWRP that I was able to flash properly vs using nouget twrp the first 2 flashes that gave me bugs each time.
Click to expand...
Click to collapse
using Oreo TWRP flash this zip will pass the saftynet test ? it is quite a problem on
android N ，it will disable the wifispot function.

OP, I love you.
If we already have the engineering aboot and TWRP flashed, can we just flash this right over (with a data/system wipe)?
I love SuperROM but I need Wi-Fi Calling to work.
EDIT: I'm an idiot, I misread your instructions. Am I correct in understanding that this is just the stock AT&T Oreo image with aboot and boot swapped out?

sheik124 said:
OP, I love you.
If we already have the engineering aboot and TWRP flashed, can we just flash this right over (with a data/system wipe)?
I love SuperROM but I need Wi-Fi Calling to work
Click to expand...
Click to collapse
yes if you are coming from rooted h910 nougat rom with twrp, you can flash this h910 oreo zip with no problem.
All the bloat from att should be there when u boot up so wifi calling should work.

sheik124 said:
OP, I love you.
If we already have the engineering aboot and TWRP flashed, can we just flash this right over (with a data/system wipe)?
I love SuperROM but I need Wi-Fi Calling to work.
EDIT: I'm an idiot, I misread your instructions. Am I correct in understanding that this is just the stock AT&T Oreo image with aboot and boot swapped out?
Click to expand...
Click to collapse
darkknight200 said:
yes if you are coming from rooted h910 nougat rom with twrp, you can flash this h910 oreo zip with no problem.
All the bloat from att should be there when u boot up so wifi calling should work.
Click to expand...
Click to collapse
Yes just 2 files changed flash right over Nougat > I recommend you use this version of TWRP > https://s3.amazonaws.com/phoenix591/us996/recovery-twrp-us996-2018-09-23.img
it's tested by @darkknight200

clsA said:
Yes just 2 files changed flash right over Nougat > I recommend you use this version of TWRP > https://s3.amazonaws.com/phoenix591/us996/recovery-twrp-us996-2018-09-23.img
it's tested by @darkknight200
Click to expand...
Click to collapse
Awesome, downloading it now. Can you confirm a cpl things?
mk2000 kernel means that we can continue using exFAT on micro SD.
Right now I have unencrypted internal and external storage, this keeps it all the same.
Updates baseband/modem to the radio that came out with Oreo.
Will post results once I'm all set back up. I was literally about to selectively flash back to stock v10v, keep TWRP and root, let it download the OTA, and then try to get updated. This is easier.

sheik124 said:
Awesome, downloading it now. Can you confirm a cpl things?
mk2000 kernel means that we can continue using exFAT on micro SD.
Right now I have unencrypted internal and external storage, this keeps it all the same.
Updates baseband/modem to the radio that came out with Oreo.
Will post results once I'm all set back up. I was literally about to selectively flash back to stock v10v, keep TWRP and root, let it download the OTA, and then try to get updated. This is easier.
Click to expand...
Click to collapse
Yes mk2k Oreo still let's u use exfat.
The zip will update all partition besides the 2 described above. So you will be on Oreo baseband modem.

Upgrade to android 12

What is the process to upgrade and keep root? Is it the same (flash magisk into partition a/b after upgrade?)
Thanks

kevkid said:
What is the process to upgrade and keep root? Is it the same (flash magisk into partition a/b after upgrade?)
Thanks
Click to expand...
Click to collapse
after flashing the ROM, you need to flash magisk.zip.. that's all brother

Spuffyffet said:
after flashing the ROM, you need to flash magisk.zip.. that's all brother
Click to expand...
Click to collapse
Isn't it possible to install magisk to inactive slot after update and before reboot any more?

epr said:
Isn't it possible to install magisk to inactive slot after update and before reboot any more?
Click to expand...
Click to collapse
Yes, you can do that as long as you do a manual install. Not if you let the System Update do a "download and install".

BillGoss said:
Yes, you can do that as long as you do a manual install. Not if you let the System Update do a "download and install".
Click to expand...
Click to collapse
So if I want to update from OOS11 to OOS12 I have to download the full image, do a manual install via system - updates - local upgrade, install magisk to inactive slot and reboot?
The way it used to be (system downloads the full image and installs it - magisk to inactive slot - reboot) is no longer working? Why? Isn't it the same?

epr said:
So if I want to update from OOS11 to OOS12 I have to download the full image, do a manual install via system - updates - local upgrade, install magisk to inactive slot and reboot?
The way it used to be (system downloads the full image and installs it - magisk to inactive slot - reboot) is no longer working? Why? Isn't it the same?
Click to expand...
Click to collapse
What you're proposing may work (the OOS 12 OTA is a full image). But with incremental OTAs you can't let the system download and install and then install Magisk to inactive. It breaks the installation.
So, your phone - do it your way and let us know the result. That we all learn something out of the process.

BillGoss said:
What you're proposing may work (the OOS 12 OTA is a full image). But with incremental OTAs you can't let the system download and install and then install Magisk to inactive. It breaks the installation.
So, your phone - do it your way and let us know the result. That we all learn something out of the process.
Click to expand...
Click to collapse
OK, thanks.
I'll try with the OTA as soon as OOS 12 is available for my region (EU, KB2003).

epr said:
OK, thanks.
I'll try with the OTA as soon as OOS 12 is available for my region (EU, KB2003).
Click to expand...
Click to collapse
I went back and read what I said in https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/ which was:
You also need to know that if you let System Update download and install a delta update, then you cannot make any changes to the updated partitions until after the phone has rebooted otherwise the update will fail.
Click to expand...
Click to collapse
So you're ok with doing what you suggested.
Ah, the joys of getting old and forgetful!

BillGoss said:
I went back and read what I said in https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/ which was:
So you're ok with doing what you suggested.
Ah, the joys of getting old and forgetful!
Click to expand...
Click to collapse
Same fits to me.
Not the youngest anymore...