Database Develop

[Q] Installing TWRP will stop me from getting OTA updates?

Hello
I bought the Note 4 from T-mobile and i'm running stock rom.
I just root the device with chainfire tool and I'm thinking to change the recovery from stock to TWRP.
I'm wondering if by doing that i will lose the ability to get OTA updates from Samsung / T-mobile.
I did a search on the forum for this question, most of the threads are a year old so i just want to make sure that the answer is the same for our new device.
Please answer just if you know for sure, Thanks

re: twrp
NirAndroid said:
Hello
I bought the Note 4 from T-mobile and i'm running stock rom.
I just root the device with chainfire tool and I'm thinking to change the recovery from stock to TWRP.
I'm wondering if by doing that i will lose the ability to get OTA updates from Samsung / T-mobile.
I did a search on the forum for this question, most of the threads are a year old so i just want to make sure that the answer is the same for our new device.
Please answer just if you know for sure, Thanks
Click to expand...
Click to collapse
You already lost the ability to receive OTA updates by rooting
the phone. If you want to get OTA updates the phone cannot be
rooted or have custom recovery like twrp.
The whole and main idea behind having twrp custom recovery
is to be able to flash custom zip file roms and mods.
With stock rooted firmware you will not be able to successfully
flash any custom roms or mods.
If you do flash any custom zip file roms using twrp
you will also loose the ability to have OTA updates.
Good luck!

First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Misterjunky said:
You already lost the ability to receive OTA updates by rooting
the phone. If you want to get OTA updates the phone cannot be
rooted or have custom recovery like twrp.
The whole and main idea behind having twrp custom recovery
is to be able to flash custom zip file roms and mods.
With stock rooted firmware you will not be able to successfully
flash any custom roms or mods.
If you do flash any custom zip file roms using twrp
you will also loose the ability to have OTA updates too.
Good luck!
Good luck!
Click to expand...
Click to collapse

NirAndroid said:
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Click to expand...
Click to collapse
If you check the OTA option and find an update, the updater
will tell you that it cannot install the update due to an unofficial
operating system or something to that effect, I forgot the exact
wording of the message. (if you're rooted)
There is a way to unroot the phone but in my opinion it's just not worth the
hassle to re-root it because as I said being rooted and having twrp recovery
will not help you much at all since you will not be able to flash any custom
roms or mods with out loosing your official stock status which needs to
remain intact in order to be able to get future ota updates.
Good luck!

NirAndroid said:
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Click to expand...
Click to collapse
Mr. Junky is correct. But why would you even want an OTA update? Even if you could it would unroot your device. If there is/was a software update it will be on here or SamMobile about the same time & you can install it manually.

NirAndroid said:
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Click to expand...
Click to collapse
You have only 2 posts on XDA and you are second guessing our replies on your question? Either believe what we answer or stick to google and don't waste our time.

NirAndroid said:
Hello
I bought the Note 4 from T-mobile and i'm running stock rom.
I just root the device with chainfire tool and I'm thinking to change the recovery from stock to TWRP.
I'm wondering if by doing that i will lose the ability to get OTA updates from Samsung / T-mobile.
I did a search on the forum for this question, most of the threads are a year old so i just want to make sure that the answer is the same for our new device.
Please answer just if you know for sure, Thanks
Click to expand...
Click to collapse
Well OTA is out of the question. But I was successful with the last update by using Kies 3.
I just had to root again afterwards using the same method.

Brava27 said:
You have only 2 posts on XDA and you are second guessing our replies on your question? Either believe what we answer or stick to google and don't waste our time.
Click to expand...
Click to collapse
No body asked you to spend your time in my thread, you are more then welcome to move a long because its clearly that you have nothing smart to say beside rasing your post counter.
For all the others, thank you for your help.
The reason that i would like to keep the OTA updates is because i love the stock rom and i dont want to check every timr on the internet if a new build has came out.
its much more easier with OTA too keep being update. But i guess my needs to be root are biger and i will need to flash the updates manually.
Once again, thank you.

I get Ota updates on mine rooted.Only thing u can't install if u have twrp will put u in a boot loop it needs the stock android recovery.You have to wait for a rom with the update

...........As long as I can remember, you root a device you lose carrier OTA updates. ..why is this so difficult for people to comprehend o_0 every new device every year it's the same questions. .......you have the capacity to root......yet you question if you'll lose OTA -_-, & most root methods have disclaimers saying you lose this x we are not responsible for brick etc. ........
Sent from my SM-N910T using Tapatalk

[Q] Pingpong root and Twrp Manager....???

Ok, so i googled a bit and do see that some people have had issues trying this, but most of the examples i was reading were on devices from carriers with locked bootloaders. Since the tmo version has an unloacked BL was wondering if anyone has tried this or not?
I was thinking of simply using flashify or twrp manager to install recovery from within my currently rooted (superuser) rom. Most people that have tried using locked bootloaders endup with a soft brick from what i have seen. Just not sure how much the unlocked bootloader would help us in this situation.
I know i can just use CF auto root but was trying to do it without tripping knox really. However, i have never had issues with any warranty through tmobile (rooted, tripped knox, whatever) and with the announcement of android pay, i am way less interested in samsung pay so tripped knox wouldnt be the end of the world... but still curious
EDIT: So apparently chainfire just released something called flashfire that appears it can do exactly what i am looking for. Anyone else looking for the same should check it out...
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433

So, this will not trip knox? I'm currently stock waiting for the 5.1 update to see if it's worth it to keep stock or root my phone. I just want to root it so bad because I could hypothetically get double battery life with the tweaks I would do. I'm interested in Samsung Pay (sorta) but if Google Wallet/Android Pay will have the same functions, then IDC.

darklime said:
So, this will not trip knox? I'm currently stock waiting for the 5.1 update to see if it's worth it to keep stock or root my phone. I just want to root it so bad because I could hypothetically get double battery life with the tweaks I would do. I'm interested in Samsung Pay (sorta) but if Google Wallet/Android Pay will have the same functions, then IDC.
Click to expand...
Click to collapse
If you install recovery no matter what method it will trip. For Roms, Flashfire won't trip as long as you don't flash boot.img aka kernel. You need to remove it before flashing

Downgrade from Lollipop to Kitkat without tripping knox SM-G900F

Hi all!!
After spending a huge amount of hours, searching the forum, I still have doubts...
Is it possible to downgrade from Lollipop, to kitkat, without tripping knox (warranty void) in the S5???
Some say, that flashing with Odin it's ok, others say that will go in a loopboot, others say that the bootloader is not compatible, and flashing a new rom will trip knox, others say that if the rom is official, will not trip knox...
What to believe??????
If there is a way to downgrade, safely and without tripping knox, please show me how, in a step-by-step process, I really appreciate it.
Here are the mobile phone data:
SM-G900F
Firmware: G900FXXU1BOD3
Thanks in advance!

Downgrade away, I have the G900F, and flashing KK over LP works fine and does not trip KNOX
You only trip KNOX by flashing custom stuff, stock ROMs are signed by Samsung so do not trip KNOX
The only issue I had was having to flash KK twice, first flash worked but wouldn't boot, flashed again, booted first time

*Detection* said:
Downgrade away, I have the G900F, and flashing KK over LP works fine and does not trip KNOX
You only trip KNOX by flashing custom stuff, stock ROMs are signed by Samsung so do not trip KNOX
The only issue I had was having to flash KK twice, first flash worked but wouldn't boot, flashed again, booted first time
Click to expand...
Click to collapse
Hi Detection!
Thank you for your enlightement, but tell me, you flashed your device using Odin, right?
Thanks!

Yep, ODIN 3.10.6

*Detection* said:
Yep, ODIN 3.10.6
Click to expand...
Click to collapse
Ok, will give it a go!
Thanks Detection!

And how did it go?? Did You safely downgraded to KK?? I was thinking about it, got my S5 with pre-installed Lollipop but without root I can't block adds and stuff - it's rather annoying.

cichy20a said:
And how did it go?? Did You safely downgraded to KK?? I was thinking about it, got my S5 with pre-installed Lollipop but without root I can't block adds and stuff - it's rather annoying.
Click to expand...
Click to collapse
You can root lollipop, but it'll trip KNOX
CF Auto Root

Yeah i know that CF-AutoRoot works on lolly but I'd rather keep my warranty void Guess no new method on gaining root w/o tripping knox was introduced to S5 design If i recall S6 is rootable now without knox messed up but no go for S5

I flashed my S5 a few months ago from 5.0 back to 4.4.2, and last week the same thing, but on my gf's Note3.
It's kind of easy and safe to do, if you do some research in advance:
- find exactly which ROM you need (the wrong one won't work and make ur phone temporarily unusable).
- download the official stock ROM
- KNOX won't trip if it's an official stock ROM.
- Boot the phone in recovery mode to wipe the cache partition and do a factory reset (after backing up the important data).
- Flash with Odin. There's many youtube tutorials on that one.
Enjoy.
If you didn't do a factory reset, wipe cache partitions etc you'll almost certainly get stuck in bootloop after flashing. In that boot up in recovery mode again, do those wipes and then restart.

*Detection* said:
Downgrade away, I have the G900F, and flashing KK over LP works fine and does not trip KNOX
You only trip KNOX by flashing custom stuff, stock ROMs are signed by Samsung so do not trip KNOX
The only issue I had was having to flash KK twice, first flash worked but wouldn't boot, flashed again, booted first time
Click to expand...
Click to collapse
gluecks said:
I flashed my S5 a few months ago from 5.0 back to 4.4.2, and last week the same thing, but on my gf's Note3.
It's kind of easy and safe to do, if you do some research in advance:
- find exactly which ROM you need (the wrong one won't work and make ur phone temporarily unusable).
- download the official stock ROM
- KNOX won't trip if it's an official stock ROM.
- Boot the phone in recovery mode to wipe the cache partition and do a factory reset (after backing up the important data).
- Flash with Odin. There's many youtube tutorials on that one.
Enjoy.
If you didn't do a factory reset, wipe cache partitions etc you'll almost certainly get stuck in bootloop after flashing. In that boot up in recovery mode again, do those wipes and then restart.
Click to expand...
Click to collapse
Hi all!
Tell me something, after flashing KK, software update is allways trying to update to LP... is there a way of avoiding this, without root access?
Thanks in advance!

you need to disable the FOTA processes, but I'm not sure you can do that without root

Ok guys so let me get this straight - I only need proper KK image, provided by Samsung (their signature and so on) with my CSC (in my case Polish XEO)? Then connect my phone with PC, start ODIN (any particular version?) and what to choose, what check and what not? Sorry for this only had HTC before (and Sony and LG but those are wifes phones) and flashing on it was a bliss, especially when You had S-OFF.

dicemaster said:
Hi all!
Tell me something, after flashing KK, software update is allways trying to update to LP... is there a way of avoiding this, without root access?
Thanks in advance!
Click to expand...
Click to collapse
Not stop, but you can delay it indefinitely by clearing the cache in recovery each time it has the update ready for you to install
Then boot back into droid, and hit the install button, which will fail because you just deleted the update in recovery
Rinse and repeat
You can root KK without tripping KNOX though, so no reason to not root it really

*Detection* said:
Not stop, but you can delay it indefinitely by clearing the cache in recovery each time it has the update ready for you to install
Then boot back into droid, and hit the install button, which will fail because you just deleted the update in recovery
Rinse and repeat
You can root KK without tripping KNOX though, so no reason to not root it really
Click to expand...
Click to collapse
Hi Detection!
I know we can root without tripping knox, but I am afraid of doing something wrong...
Can you tell me how to do it, in a safe way???
Thanks in advance!

dicemaster said:
Hi Detection!
I know we can root without tripping knox, but I am afraid of doing something wrong...
Can you tell me how to do it, in a safe way???
Thanks in advance!
Click to expand...
Click to collapse
Either make sure your KK ROM is a pre June 2014 build, if not, either flash with ODIN, or read up on how to downgrade only the Kernel to a pre June 2014 KK kernel, then use towelroot app to root it, and flash your original Kernel back
All the info you need is here on XDA, might take a bit of reading, but you should really learn as much as you can before blindly flashing things anyway

I read in another thread, someone said that if your S5 came with LP out of the box, you can't downgrade to even official samsung KK without tripping knox. I'm not sure how true is this or whether that person is just blowing smoke.

question about maintaining root

So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!

bluesrph said:
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
Click to expand...
Click to collapse
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/

saurabh40629 said:
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Click to expand...
Click to collapse
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs

bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Click to expand...
Click to collapse
Dm-verity u can bypass but bootloader one, you can not. Look at the apps, mods section.

bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
You shouldn't try to flash the partial OTAs while you are rooted and have a custom recovery installed. The partial zip will try to make specific changes in the restricted partitions (/system, /boot, /recovery, etc.) related to the update and prior modifications to these files may cause the update to fail and the phone to brick. You can still use the "Update" tab in the Settings menu to download the update though as OOS will detect root and download the full zip of the update for you. Simply flash the full zip in TWRP, wipe cache/dalvik, then flash SuperSU and you're good to go the next time an update rolls out. Updating by this method (rooting immedately after flashing update) will also prevent OOS from replacing TWRP with the stock recovery again. When you download the update, you'll know if it's the full zip if the file is >1 GB (they're usually ~1.4 GB,, whereas the partial zips are a few hundred MB).
Unlocked bootloader warning screen is cannot be removed without relocked and fully resetting (wiping) the phone. DM-verity warning screen can be removed by following this guide. Make sure that you are flashing the correct firmware for you current version of OOS though, flashing the wrong version can brick you phone.

Can a rooted phone be updated?

Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?

ChronosTrigger said:
Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?
Click to expand...
Click to collapse
No, it fails to install. You need to reflash the stock boot image to take an OTA.

Confused still
CurtisMJ said:
No, it fails to install. You need to reflash the stock boot image to take an OTA.
Click to expand...
Click to collapse
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?

ChronosTrigger said:
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?
Click to expand...
Click to collapse
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)

CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
WARNING: This file is really intended for a developer to use in making a rooted slot. Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? Although, mostly likely, it won't flash at all if you are rooted.
I used adb to capture the Razer Phone 2 MR2 OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5

translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?

ChronosTrigger said:
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?
Click to expand...
Click to collapse
Not quite... The update will likely fail to apply due to checksum failures. If it did go through it would probably brick the kernel so that's a good thing. Sorry, there's not really a way to automatically root after official OTAs as they update block by block between two known states, and neither is rooted. It's just sort of not possible, by design. You have to unroot, update and root again.
The OTA package translucentfocus has provided allows us to reproduce a single slot before the week's wait for the factory image so we can root sooner.

translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
which OTA is this? Also how to update

xterminater07 said:
which OTA is this? Also how to update
Click to expand...
Click to collapse
Sorry, I didn't specify. It's the MR2 update for the Razer Phone 2. Original reply has been also updated with version information in bold.
How to update? Actually, I posted the OTA because it's really for someone to make a slot with root before Razer releases the Factory MR2 Images--as @CurtisMJ mentioned previously.

CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks

Univsoldur said:
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks
Click to expand...
Click to collapse
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)

CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
CurtisMJ said:
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)
Click to expand...
Click to collapse
Thanks for the detailed response I managed to get up with the previous owner on swappa last night. He told me he unlocked the phone but never actually got around to rooting it. He also said it is running stock and the reason magisk is still on the phone after a wipe is because magisk persists after a wipe.
Messages from him.
Sorry about that, I did unlock the bootloader but I never actually got around to rooting. I usually relock the bootloader before I sell it but I completely forgot. You can apply an ota because I never installed a custom recovery, something else I didn't get around to doing. You can easily relock the bootloader using adb. If you need help with this let me know and I can walk you through it. But the bootloader being unlocked has zero effect on ota's. You are all good to go as far as that goes.
Oh no you're absolutely fine with an ota. I just looked it up and you're absolutely right, magisk does survive a reboot now. Since I didn't load a custom recovery though an ota will install just fine. Although when an ota does install though it will most likely remove magisk because it will write over the boot.img with the factory one. Here is the link to the factory images. It includes instructions on how to install it. But honestly a new ota should be released any time now since the last one I think was November. Once that installs you will be completely back to stock.
Does this sound accurate to y'all. Thanks again

@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.

CurtisMJ said:
@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.
Click to expand...
Click to collapse
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?

I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?

Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
Yes, that will return it to stock and remove Magisk. No, if you flash the factory image you don't need to do anything further with the kernel.
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
DrGonzo6o said:
I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?
Click to expand...
Click to collapse
The bootloader needs to be unlocked, yes. I had the unlocked one from the start, so I can't comment on how well that will work though.
Has anyone with an AT&T version successfully flashed unlocked firmware?

Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
I did post a full unroot guide...