Database Users

[Q] How to use SuperSU?

Hi,
I got an update on my LG G2 D802 and i have ROOT, i downloaded SuperSU because someone told me that i can update my device with it, but i dont know how.
Can someone explain me how to use it? what should i do in the SuperSU to update my device?
Thank you.

Uh...i don't think supersu can update your device. All it does is handle root.
Gesendet von meinem LG-d802 mit Tapatalk

ckyy said:
Uh...i don't think supersu can update your device. All it does is handle root.
Gesendet von meinem LG-d802 mit Tapatalk
Click to expand...
Click to collapse
But i saw that it have OTA Survival in the Settings.
Are you sure that i cant to update with it?
On my previous theard i asked if i can update, and someone told me that he updated his G2 with the SuperSU, but i dont know how to do this too..

itaylubo2 said:
But i saw that it have OTA Survival in the Settings.
Are you sure that i cant to update with it?
On my previous theard i asked if i can update, and someone told me that he updated his G2 with the SuperSU, but i dont know how to do this too..
Click to expand...
Click to collapse
OTA survival means that when your carrier sends out an OTA update for your device, you should still have root afterwards. Normally without OTA survival you will lose root after updating. SuperSU has nothing to do with updates, it is simply a firewall between apps and the root of your device. :good:

If you have OTA survival turned on in SuperSU, AND you have stock recovery, then theoretically, you can do the OTA update and still have root when it's finished. But it isn't 100% successful.

Also OP...
http://forum.xda-developers.com/showthread.php?t=2443934

souleman said:
If you have OTA survival turned on in SuperSU, AND you have stock recovery, then theoretically, you can do the OTA update and still have root when it's finished. But it isn't 100% successful.
Click to expand...
Click to collapse
I have stock recovery, so i should turn on the OTA Survival in the SuperSU and to start to update?
I saw in the settings of the SuperUser that it have also OTA Survival, should i turn it on too?
Thank you.

DO NOT DO OTA'S IF YOU ROOTED. Period.

khaytsus said:
DO NOT DO OTA'S IF YOU ROOTED. Period.
Click to expand...
Click to collapse
I received an ota last night (whilst very drunk) . I have a rooted but otherwise completely stock rom with stock recovery and the ota installed without a problem and I remained rooted even though I hadn't set my superSU to maintain root. My system updated from 10a to 10f.
It would appear that an ota will install with root as long as you have stock recovery and have not made changes to the system partition. (apart from the su binary of course.)

bobsie41 said:
I received an ota last night (whilst very drunk) . I have a rooted but otherwise completely stock rom with stock recovery and the ota installed without a problem and I remained rooted even though I hadn't set my superSU to maintain root. My system updated from 10a to 10f.
It would appear that an ota will install with root as long as you have stock recovery and have not made changes to the system partition. (apart from the su binary of course.)
Click to expand...
Click to collapse
Yes, but I like to keep things simple for people.
Recovery is what will get you, or a modified ROM. But.. Ah, it doesn't matter, people will do it anyway.

itaylubo2 said:
I have stock recovery, so i should turn on the OTA Survival in the SuperSU and to start to update?
I saw in the settings of the SuperUser that it have also OTA Survival, should i turn it on too?
Thank you.
Click to expand...
Click to collapse
You shouldn't have SuperSU and SuperUser both on the phone. Remove one of them (probably SuperUser as it doesn't play well with some things).
It is recommended not to do an OTA if you are rooted. If you wait a few days, someone will have a flashable version of the OTA on here.
Having a modified stock rom very rarely causes any issues. It can, but it doesn't very often. 99% of the time, it's because someone is running a different recovery, and still blames it on the ROM. But unless your ready to flash it back to how it was when you opened the box, just wait a couple days.

souleman said:
You shouldn't have SuperSU and SuperUser both on the phone. Remove one of them (probably SuperUser as it doesn't play well with some things).
It is recommended not to do an OTA if you are rooted. If you wait a few days, someone will have a flashable version of the OTA on here.
Having a modified stock rom very rarely causes any issues. It can, but it doesn't very often. 99% of the time, it's because someone is running a different recovery, and still blames it on the ROM. But unless your ready to flash it back to how it was when you opened the box, just wait a couple days.
Click to expand...
Click to collapse
But i have stock recovery and stock ROM, it is matter?
I realy dont know what to do when the Kitkat 4.4 will comes...

itaylubo2 said:
But i have stock recovery and stock ROM, it is matter?
I realy dont know what to do when the Kitkat 4.4 will comes...
Click to expand...
Click to collapse
To be safe you could always unroot your phone before updating since everything is stock you won't be losing much and you won't be taking any unnecessary chances. Plus the root might not stick with such a big update even with root survival so you might have to reroot it again after the update anyways.
This is pretty much the same thing everyone had already said, I don't think anyone here would tell you it's worth taking the risk -even if it's just a slight risk since you don't have a custom recovery installed- that will only be saving you the few minutes it'll take to reroot your phone.
Sent from Sprint LG G2

kcerica said:
To be safe you could always unroot your phone before updating since everything is stock you won't be losing much and you won't be taking any unnecessary chances. Plus the root might not stick with such a big update even with root survival so you might have to reroot it again after the update anyways.
This is pretty much the same thing everyone had already said, I don't think anyone here would tell you it's worth taking the risk -even if it's just a slight risk since you don't have a custom recovery installed- that will only be saving you the few minutes it'll take to reroot your phone.
Sent from Sprint LG G2
Click to expand...
Click to collapse
How i Unroot my phone? just doing Factory Reset?

There should be an unroot option in the supersu settings
Sent from Sprint LG G2

itaylubo2 said:
How i Unroot my phone? just doing Factory Reset?
Click to expand...
Click to collapse
Uninstall SuperUser, then in SuperSu there is an option to unroot the phone.

souleman said:
Uninstall SuperUser, then in SuperSu there is an option to unroot the phone.
Click to expand...
Click to collapse
I downloaded SuperSU, and after i delete it.
and i did Reboot, and the Superuser dissapeard, but i still have ROOT, i can use Freedom, Market Unlocker and Auto Hide Soft Keys.
Now i downloaded SuperSU again, and i saw in the "Description" that the SuperUser should be removed when i download the SuperSU.
If i'll do Full Unroot from the SuperSU, it will work on LG G2 D802 with stock ROM&Recovery?
Thank you very much !!!

itaylubo2 said:
I downloaded SuperSU, and after i delete it.
and i did Reboot, and the Superuser dissapeard, but i still have ROOT, i can use Freedom, Market Unlocker and Auto Hide Soft Keys.
Now i downloaded SuperSU again, and i saw in the "Description" that the SuperUser should be removed when i download the SuperSU.
If i'll do Full Unroot from the SuperSU, it will work on LG G2 D802 with stock ROM&Recovery?
Thank you very much !!!
Click to expand...
Click to collapse
Yup. Full Unroot in SuperSu will delete the files from the /system partition that give you access to root.

souleman said:
Yup. Full Unroot in SuperSu will delete the files from the /system partition that give you access to root.
Click to expand...
Click to collapse
It will work for 100%? In the Root Exporer, i search in the /system/bin for the "su" and i didnt found it, also i didnt found the SuperUser.apk in the /system/app, i can find only in the /system/xbin the "su" file.
It should be like this? because i saw some videos on Glalaxy Note 2 that he have all except the su file in the /system/xbin..

itaylubo2 said:
It will work for 100%? In the Root Exporer, i search in the /system/bin for the "su" and i didnt found it, also i didnt found the SuperUser.apk in the /system/app, i can find only in the /system/xbin the "su" file.
It should be like this? because i saw some videos on Glalaxy Note 2 that he have all except the su file in the /system/xbin..
Click to expand...
Click to collapse
There shouldn't be an su files after unroot. Is either superuser.apk or supersu.apk in either /system/app or /data/app?

Root not sticking! Need professional help.

Good evening ladys and gentlemen,
hoping you can help me with my root-not staying-problem.
I have the A2017G B09 version. I already managed to unlock my device and I had root with xposed installed.
Sounds good so far, right?
Well my problem is that after the restart that is needed to activate my xposed modules, my root went away and I couldn't get it back. After that I tried to do it again but root wouln't stick no matter what.
And yes, I did use the "reboot disemmcwp" command.
I tried to root by flashing the newest chainfire supersu 2.79, since I have newest twrp 3.0.3-1.
It would be great if you would be able to help me on my journey and maybe explain to me the difference between systemless and normal, and what magisk is since I saw that op up a few times.
Oh and please tell me from where I should start if I want to work on everything android related (roms, kernel, apps) since my semsester is nearing its end.
Thanks in advance.

Systemless root means that the /system partition is not modified, however the boot image is altered. There is much hype on this, however there still are many mods out there requiring modifications of /system. I personally do not see any advantage of it, probably because I have been using custom ROMs for years, and custom ROMs has many alterations to the /system compared to stock or pure CM or AOSP roms. However it is clear that the future goes that way and eventually most of the mods will be systemless. The advantage is that you will supposedly be able to flash OTA upgrades, however if the OTA is also modifying the boot partition, then it doesn't matter, you will not be able to flash the OTA upgrade. So the benefits of systemless mods are arguable.
Magisk is an open root. it is systemless from the beginning and any module under Magisk framework will be systemless. So far no official Magisk release (latest at this time is v10.2) is compatible with the Axon stock ROM. However, the latest v10.3-beta2 seems to fix the root injection problem. It is included in the Bad Boyz custom ROM.
There are some apps not working on root devices. They use a SafetyNet procedure to check for that, such as Android Pay or Pokemon Go. However there are ways to overcome this security check and you can enjoy root and SafetyNet compatibility either using SuperSU or Magisk, system or systemless root. the issue becomes a little tricky when adding Xposed mod framework to the mix, since the procedures to have all 3 (root, SafetyNet and Xposed) working is not that straightforward. However this is possible in the Axon 7. You can find one of my guides in the links in my signature.
Enjoy!!!!

Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.

Try reflashing supersu don't reboot, then use terminal in TWRP to do reboot disemmcwp and see if it works. I usually use root Explorer to see if I can change /system to r/w. If it did not work go back to terminal in TWRP and try again. I have had to do it a few times to get it to work. Using adb terminal seems to work first time, terminal apps have not worked for me.

Yuujinz said:
Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.
Click to expand...
Click to collapse
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.

Oki said:
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.
Click to expand...
Click to collapse
Wouldn't it brick my european device?

Yuujinz said:
Wouldn't it brick my european device?
Click to expand...
Click to collapse
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484

Oki said:
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Click to expand...
Click to collapse
Ok thanks I'll do it this evening
Or maybe not, to risky.

Installing Official Nougat in an XT1621

Hello! Today I woke up with the notification of the new nougat update, Exciting! But I guess I have several problems: first of all, my phone is rooted, will I lose root acces? Also, I have TWRP installed. Yesterday I tried installing a security update on a device with TWRP and there was no way, will this happen to me? Another problem is my kernel, ElementalX. I've installed it since I had screen burn, but I don't really care about performing a fix everyday, but I know this kernel will prevent Nougat to install correctly. I do have a System Backup from when the kernel was not installed, and I read you can install 'just the boot.img' from TWRP restoring options but there's no "boot.img" file on my backup folder. I would like to add that I'm running on Marshmallow 6.0.1, rooted with SuperSU, using Xposed. The ElementalX kernel ver. is 3.10.84-ElementalX-G4-0.07 and the TWRP ver. is twrp-3.0.2-0-athene. Thank you all in advance!

polykiwi316 said:
Hello! Today I woke up with the notification of the new nougat update, Exciting! But I guess I have several problems: first of all, my phone is rooted, will I lose root acces? Also, I have TWRP installed. Yesterday I tried installing a security update on a device with TWRP and there was no way, will this happen to me? Another problem is my kernel, ElementalX. I've installed it since I had screen burn, but I don't really care about performing a fix everyday, but I know this kernel will prevent Nougat to install correctly. I do have a System Backup from when the kernel was not installed, and I read you can install 'just the boot.img' from TWRP restoring options but there's no "boot.img" file on my backup folder. I would like to add that I'm running on Marshmallow 6.0.1, rooted with SuperSU, using Xposed. The ElementalX kernel ver. is 3.10.84-ElementalX-G4-0.07 and the TWRP ver. is twrp-3.0.2-0-athene. Thank you all in advance!
Click to expand...
Click to collapse
You must return to stock recovery and stock kernel in order to flash the OTA. Yes you will lose root and will have to redo it once you are updated. The procedure for rooting in Nougat is different than on Marshmallow. There are numerous posts in this forum on the exact steps you need to take to accomplish all of this this safely. Take the time to read and research before you try anything. Don't just expect somebody to spoon feed you the info.

pastorbob62 said:
You must return to stock recovery and stock kernel in order to flash the OTA. Yes you will lose root and will have to redo it once you are updated. The procedure for rooting in Nougat is different than on Marshmallow. There are numerous posts in this forum on the exact steps you need to take to accomplish all of this this safely. Take the time to read and research before you try anything. Don't just expect somebody to spoon feed you the info.
Click to expand...
Click to collapse
Thanks! I'm installing it tomorrow!

EngineerMode unroot?

back when engineermode exploit backdoor 'thing' whatever you want to call it, was still a thing i seized to opportunity to gain root access, however since then magisk hide has begun failing me and i would like to either find a way to update magisk from v14.0 safely, or to unroot completely (preferably without wiping) as this has started being problematic. I am on the latest oxygenOS update and i used this guide to root (i originaly linked it here but apparently i cant do that, it was on github, called OneplusRoot by a fella named aldur.)
If anyone can help id really appreciate it.
Thanks in advance

Since One Plus removed engineering mode I'm surprised you were able to update OOS and maintain the exploit. Why don't you just unlock your bootloader and root the proper way? Your phone won't melt if you do.

I would like to avoid wiping if possible. I too am surprised at the persistence of root after at least 3 OTAs. At this point I no longer really need root and would rather my phone run smoothly without some applications crashing or not running due to root.

bump?

gbesh said:
bump?
Click to expand...
Click to collapse
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you

manor7777 said:
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
Click to expand...
Click to collapse
Well my system doesn't boot with root. I have to manually mount something and start the magisk service.
Which is why I'm not sure how to update as I've been told the updated version has a different file structure that the one I'm on.

were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how

yohouse2 said:
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
Click to expand...
Click to collapse
no unfortunately i am still waiting for a solution.

gbesh said:
no unfortunately i am still waiting for a solution.
Click to expand...
Click to collapse
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install

yohouse2 said:
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
Click to expand...
Click to collapse
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.

gbesh said:
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
Click to expand...
Click to collapse
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.

yohouse2 said:
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
Click to expand...
Click to collapse
After one of the recent updates, magisk hide started working again and my apps are no longer crashing. It is strange but i guess this situation has turned out favourably after all.

updating to latest OTA 11.0.1.1.IN11AA

I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.

cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
Update using local, dont reboot - go to magisk; install to inactive slot(after OTA) *disable module to be safe - Then restart

cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it

dladz said:
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
Click to expand...
Click to collapse
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?

cubeplayer1 said:
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
Click to expand...
Click to collapse
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?

I'm rooted with an unlocked bootloader on 11.IN11AA (Global). How do I perform a local upgrade without the OTA file to put into the root folder? It seems like the Global version of the OTA file is nowhere to be found and I can't download it via System Update since it fails due to root. Do we need to just wait for the 11.0.1.1.IN11AA OTA zip file to be posted? Thanks in advance.

Yes, looks like we are in waiting mode for it to show up...

dladz said:
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
Click to expand...
Click to collapse
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.

cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
You'd have to install locally even with oxygen updater.

galaxys said:
Yes, looks like we are in waiting mode for it to show up...
Click to expand...
Click to collapse
Yea I guess that's why Oxygen Updater isn't showing anything new for me. Once it shows up on the internet, I'm sure the OU app will refresh and show an available update.

cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.

cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).

dlhxr said:
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
Click to expand...
Click to collapse
Thanks for these steps, it worked for me. After I flashed Magisk via the Magisk App to the inactive slot, I rebooted and had the latest version installed with root preserved. :highfive:

After I did it I'm getting the com.android.phone stopping and my Sims aren't recognized. I cleared cache, phone and SIM toolkit but didn't work. Grrrrr

I'm a rooted global user and update has never showed until today. It was only 405mb and Google play services was showing the update. Oxygen updater shows nothing and system update shows nothing. I'm gonna wait to see what happens since it's not a full update

Same here global 406 mb ota. It's like not recognizing we have root...

bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
Good looking out bro, that worked a charm. :good:

bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
^^^^^^This -- easiest and fastest root upgrade I have ever done on any device.
Magisk is now built to do it this way.

bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
This worked for me as well taking the actual partial OTA update from system update and going through the steps in Magisk.
A little nerve wracking considering the many times trying to update has failed on my last couple OP devices, but at least this time, it worked.
Thanks.

anyone have a patched magisk boot for IN2025?
I did the steps of flashing the stock boot.img, then booting the patched img, installed the OTA, used magisk to patch before reboot, but when it rebooted it said installation failed, and i was unable to access magisk after that as it was on the wrong slot... I had to apply the OTA update again, and now am stick without root
IN short, need either a stock IN2025 boot image to patch myself, or a magisk patched one...
TIA