Database Develop

[Q] Unroot for OTA Update

Hi and sorry if i'm wrong here, but i am not able to write in the dev directory, yet.
I unlocked and rooted my phone but now i am not able to update to the new OTA 39002 version.
Is there a way for a temporary unroot or something like this? Because i want to keep my root!
Thank you for help.

baxxter106 said:
Hi and sorry if i'm wrong here, but i am not able to write in the dev directory, yet.
I unlocked and rooted my phone but now i am not able to update to the new OTA 39002 version.
Is there a way for a temporary unroot or something like this? Because i want to keep my root!
Thank you for help.
Click to expand...
Click to collapse
With something like this:
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=fr
But root should not prevent for an OTA update

Le_Poilu said:
But root should not prevent for an OTA update
Click to expand...
Click to collapse
Thanks for fast answer.
I thought the same, but when it is starting up to update in the middle it shows the "dead" android with the red "!" , you know.
after that the phone boots normaly and it says "not successfull"...
i already tried some times...
I will try the rootkeeper, thanks for that again.

baxxter106 said:
Thanks for fast answer.
I thought the same, but when it is starting up to update in the middle it shows the "dead" android with the red "!" , you know.
after that the phone boots normaly and it says "not successfull"...
i already tried some times...
I will try the rootkeeper, thanks for that again.
Click to expand...
Click to collapse
Have you change some file (like to disable camera sound ) ?
I've the same issue with OTA, and I revert all changes I've made in the past, and it work.

If you rooted your Device by changing the Kernel, you have to flash the Boot signed of the Base FW (32 i guess).
The update compares the Base Rom and the Root Exploit set you an secured Kernel, that doesn't match with the System > Problem solved.
The Root won't deny the Update. You can temp. unroot with the ported Rootkeeper (thanks to Mattlgroff) and restore the Root after the Update.
But the Boot.img must fit!

I think i did not change something. Except the kernel that came wih the rooting by mattlgroffs tool.
So i need to change the kernel with a recovery kernel via adb?
Could somebody tell me the comands? (With cwm on a SGS was it a bit easier )
Sent from my XT890 using xda app-developers app

Yes, you have to use fastboot for it (it's in the Folder of the root exploit)
Download your current FW, unpack it and copy the Boot_signed into the Root folder. Then open the cmd window, navigate to the Root Folder by cd command.
Flash the image by
Fastboot flash boot boot_signed.
Alternate you can rename it to razr_i_boot.img and overwrite the secured Kernel in the Exploit. Than just root again and it will flash the right secured Kernel.

Thank you. I will try that today. Btw. where can i find mattlgroffs root keeper? The version in the play store does...nothing?
Sent from my XT890 using xda app-developers app

http://forum.xda-developers.com/showthread.php?p=34248515

I do not want to take OTA system updates...

I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?

LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.

LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
Root solved your problem ha ha

simms22 said:
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.
Click to expand...
Click to collapse
And sometimes, even if one is 100% stock, those pesky OTAs won't install.

cam30era said:
And sometimes, even if one is 100% stock, those pesky OTAs won't install.
Click to expand...
Click to collapse
right. any system file changes prevent install.

Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?

Install a custom recovery. Done. OTAs require the stock recovery in order to flash files.

LaTropa64 said:
Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?
Click to expand...
Click to collapse
itll only attemp if you let it(it needs your approval to update), otherwise itll only tell you that an update is available. if you let it, itll try, but fail. if you boot up, youll be where you were before.

Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?

LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
you can always look at your android version in aboy phone, to see if it updated or not.

LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
You'll find update or not optimizing apps happens a lot especially if you clear cache etc...
Your fine otas can't install with root
Just flash twrp it will cone in handy incase you brick it one day you'll have twrp to fastboot fix or sideload a rom to recover from.
ONE NOTE: Never ever ever relock your bootloader with the toolkit you'll be screwed. Always leave bootlaoder unlocked. I just had to rma manufacturer phone replacement I relock mine with toolkit and couldn't flash stock firmware or oem unlock again.
Sent from my LGMS769 using XDA Free mobile app

simms22 said:
you can always look at your android version in aboy phone, to see if it updated or not.
Click to expand...
Click to collapse
I'll take a look the next time I get over there. It's not my phone, I just set it up for someone with accessibility issues and wanted it to stay the same as the day I set it up but apparently it's not done that.

OJ7 root.

After reading dozens of threads I'm at a loss.
1. Can I root?
2. If I root, is my phone still going to work? Or will it become the latest victim of my Beowolf.

Odin twrp then install unikernel inside twrp. Will trip Knox so Samsung pay won't work anymore.

tyrone1 said:
Odin twrp then install unikernel inside twrp. Will trip Knox so Samsung pay won't work anymore.
Click to expand...
Click to collapse
Ok thanks. Not concerned with Sam pay. Citibank and Wells aren't supported.

It works with Citibank cards

stncldtex said:
After reading dozens of threads I'm at a loss.
1. Can I root?
2. If I root, is my phone still going to work? Or will it become the latest victim of my Beowolf.
Click to expand...
Click to collapse
I finally found a routine and the right files needed to successfully acquire root, twrp, and custom ROM. Although, the only custom ROM Iv'e been able to boot and setup with all T-Mobile services intact and even the finger print security feature working, is the "OZOP_EDGE_v11_DOJ7.zip, thanks to stangdriver44".
Just remember you should back up the EFS and backup the phone using Samsung smart switch. If you need help, pm me. Id lay out the exact steps I took to get root originally and what it took to get out of a bricked phone, and finally to root and install a custom ROM.
I will type up what I did later today or tomorrow and post it in case anyone does the same thing to gets bootloops and bricks.
I have to attend to other chores now before I go back to work tomorrow, since I spent every evening for the last week and all day and night yesterday, trying to bring this phone out of brick.
chevy383surfing

tyrone1 said:
It works with Citibank cards
Click to expand...
Click to collapse
Sorry Capital One not Citi.

stncldtex said:
After reading dozens of threads I'm at a loss.
1. Can I root?
2. If I root, is my phone still going to work? Or will it become the latest victim of my Beowolf.
Click to expand...
Click to collapse
chainfire's systemless root BETA v2.61 works flawlessly: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

pm me.
Id like to know the steps you took to root your s6. pm me whenever possible. Thanks.
chevy383surfing said:
I finally found a routine and the right files needed to successfully acquire root, twrp, and custom ROM. Although, the only custom ROM Iv'e been able to boot and setup with all T-Mobile services intact and even the finger print security feature working, is the "OZOP_EDGE_v11_DOJ7.zip, thanks to stangdriver44".
Just remember you should back up the EFS and backup the phone using Samsung smart switch. If you need help, pm me. Id lay out the exact steps I took to get root originally and what it took to get out of a bricked phone, and finally to root and install a custom ROM.
I will type up what I did later today or tomorrow and post it in case anyone does the same thing to gets bootloops and bricks.
I have to attend to other chores now before I go back to work tomorrow, since I spent every evening for the last week and all day and night yesterday, trying to bring this phone out of brick.
chevy383surfing
Click to expand...
Click to collapse

andrey1186 said:
Id like to know the steps you took to root your s6. pm me whenever possible. Thanks.
Click to expand...
Click to collapse
I will get a write up of the steps. I'll pm you tomorrow afternoon. I planned to do it tonight, but I have a case of the Mondays!

muniz_ri said:
chainfire's systemless root BETA v2.61 works flawlessly: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
How do you flash it?

stncldtex said:
How do you flash it?
Click to expand...
Click to collapse
Install twrp on stock oj7 then flash supersu v2.61 in twrp. that's it.

muniz_ri said:
chainfire's systemless root BETA v2.61 works flawlessly: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
Does this trip KNOX?

chip.hughes said:
Does this trip KNOX?
Click to expand...
Click to collapse
of course

stncldtex said:
How do you flash it?
Click to expand...
Click to collapse
You'd have to setup Cygwin software to make the zip an 'Odin flashable .tar.md5 type file', which I have not had time to play with, in order to flash supersu zip files onto the samsung phones.
I am working on a worksheet right now explaining what I had to do to install 5.1.1 firmware and root the phone. I am still looking back to remember exactly how I unlocked the bootloader. I did have to use an android terminal to map out the twrp recovery manual on the phone itself. I do know it would wise for anyone interested in this to backup the EFS before anything. I had to download a specific windows DOS software that does it in a couple seconds and stores it on your computer. It works for a number of other phones as well. Also need to download the newest Odin 3.10.7 software in order to work with 5.1.1 firmware without any problems. Also need to do a backup of whole phone with samsung smart switch "takes place of Kies software now". When I get home tonight I will get names and locations of everything and inform everyone. If you download the wrong DOJ7 software or firmware you'll mess up your device. It took me a week to find the right software downloads related to 5.1.1 in order to make everything work right. And I did everything within 15 minutes. Once I figured out the routine.
Once you update to 5.1.1 I know of no way to downgrade.
I do recommend going over to serio22's post -[Firmware][Bootloader & Modems][Odin] - G920T - DOJ7-
And download DOJ7 BL and DOJ7 modem and G920TUVU3DOJ7 (firmware). Download Chainfire's latest beta super su.

You can just flash unikernel to get root.
Possibly any of the other kernels too

stncldtex said:
After reading dozens of threads I'm at a loss.
1. Can I root?
2. If I root, is my phone still going to work? Or will it become the latest victim of my Beowolf.
Click to expand...
Click to collapse
Yes you can root .. by flashing unikernel .. and phone will still be working ...

Tried flashing Uni through Odin with no luck. I get this in Odin.
Get PIT for mapping.
Write operation failed.
Any idea's?

stncldtex said:
Tried flashing Uni through Odin with no luck. I get this in Odin.
Get PIT for mapping.
Write operation failed.
Any idea's?
Click to expand...
Click to collapse
I recommend you root with the latest Supersu beta v2.62-3 zip. It will patch the stock kernel which was designed for your specific build unlike the unikernel. Just flash via twrp.

muniz_ri said:
I recommend you root with the latest Supersu beta v2.62-3 zip. It will patch the stock kernel which was designed for your specific build unlike the unikernel. Just flash via twrp.
Click to expand...
Click to collapse
TWRP gives off the same error.

stncldtex said:
TWRP gives off the same error.
Click to expand...
Click to collapse
More accurately trying to Odin TWRP.

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...

Secure Folder Not Starting

Hi, on android 13 no root, secure folder won't start at all eve after giving all permission manually to the app, clear data and cache, same thing, any ideas !

Have you rooted in the past? Does Samsung Pass work?

ShaDisNX255 said:
Have you rooted in the past? Does Samsung Pass work?
Click to expand...
Click to collapse
yes i was rooted before (on android 12) but i flashed a new firmware manualy odin. but now, not rooted, but bootloader unlocked. and yes samsung pass works

Pro Cal said:
yes i was rooted before (on android 12) but i flashed a new firmware manualy odin. but now, not rooted, but bootloader unlocked. and yes samsung pass works
Click to expand...
Click to collapse
Having rooted once in the past is enough to invalidate Secure Folder forever even if you go back to stock

ShaDisNX255 said:
Having rooted once in the past is enough to invalidate Secure Folder forever even if you go back to stock
Click to expand...
Click to collapse
i don't think that it applys coz even on Android 12 i was rooted, when back on stock it was working fine. that why i find it wierd. now the security patch is updated i cannot go back to android 12

Pro Cal said:
i don't think that it applys coz even on Android 12 i was rooted, when back on stock it was working fine. that why i find it wierd. now the security patch is updated i cannot go back to android 12
Click to expand...
Click to collapse
It still apply.
Knox is trip no matter what if you root your phone and Secure Folder need Knox.

Lock your bootloader and check if it works