Database Users

Magisk v11.6 compatible with Droid Turbo Stock ROM

I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Pics or it didn't happen

And last, but certainly not least...

So I can root without unlocking the bootloader using sunshine?

Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.

Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.

Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.

Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.

Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.

TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.

Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.

More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU

y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.

TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?

y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.

It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^

Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).

.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.

I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.

Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?

September Update is up now

Take a look here: https://developers.google.com/android/images
Download it now!!

Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!

Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)

ApoelEllhnwn said:
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)
Click to expand...
Click to collapse
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.

wish someone would make the factory images Flashable. All this needing a computer to update is getting old!

Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I'm sorry I must not have been very clear. My ask was for someone to try the process detailed in the link I provided in my quote above. This is supposed to allow you to uninstall Magisk (don't reboot), take the OTA as you normally would on unrooted phone, and once it installs, apply Magisk to the new slot w/ the OTA installed, then reboot. No computer needed. As I stated above, I would do it, but have yet to get the update thru the Check System Update. I am well aware of how to install it manually, as I have done that process for every update. I just saw that the linked process was updated for Magisk 17.0+ and hoped it could be verified to work. Meaning this would simplify the monthly update process tremendously.

kolothuk said:
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.
Click to expand...
Click to collapse
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.

kittygotwet said:
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.
Click to expand...
Click to collapse
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.

davidisflash said:
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.
Click to expand...
Click to collapse
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.

kittygotwet said:
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.
Click to expand...
Click to collapse
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.

davidisflash said:
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.
Click to expand...
Click to collapse
I actually figured it out. I had to use the Magisk uninstaller to remove any remaining Magisk, I guess, before I can reinstall. Now I just have another issue on the Pixel 2 9.0. Converting any user app to system app corrupts the phone.

Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I will try this guide as soon as the OTA is available.

I got another update today on my Pixel 2, which said: critical bug and performance fixes... I wonder what it is? The phone isn't as smooth after this and some glitches with youtube in landscape, there white nav bar appears, but I can't click 3 dots menu to adjust quality for example. I have to turn the phone in portrait and then do it.

razorsbk said:
I will try this guide as soon as the OTA is available.
Click to expand...
Click to collapse
I'm also still waiting for the Update ...is that normal to wait that long time?

No, it's not. Other manufacturers have released their patches via OTA.
Sent from my Pixel 2 using Tapatalk

So you think we have to sideload the patch?

How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?

Ashyford said:
How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?
Click to expand...
Click to collapse
You can't. Google is no longer releasing OTAs for 8.1. Your best bet is to use a custom kernel such as FlashKernel, as I believe it is backwards compatible, and Nathan streamlines the security patches from both Google and the Linux kernel fork into his kernel.

Did anyone else got the OTA ? I'm still wainting

Can't root 9.0.12

Hi all,
I followed the guide to update a rooted device but it didn't work I lost root. But even after flashing magisk 17, 18 and 18.1 I still can't get root.
Any advice or tips? Are you having the same problem?

Do you have the Magisk Manager app installed?

Ismael034 said:
Do you have the Magisk Manager app installed?
Click to expand...
Click to collapse
That is another strange thing... I don't see the app, but when I want to install it again it says 'Do you want to install the update...' [emoji848] and that fails... [emoji848][emoji848][emoji848]

Sometimes when you reboot the phone it appears

superiscch said:
That is another strange thing... I don't see the app, but when I want to install it again it says 'Do you want to install the update...' [emoji848] and that fails... [emoji848][emoji848][emoji848]
Click to expand...
Click to collapse
Any update? I seem in same boat ...on 9.0.12, some root apps work (torbot, liveboot) but AdAway says not rooted. Malwarebytes says rooted. Su command in terminal gets denied.....
This
Blows
As far as magisk manager it disappeared and apk install fails....

Sometimes magisk manager can get hung up in the update and then it doesn't want to let you in. Force stop, and see if i will let you in. Didn't work for me but you never know. I had to get it to where it was refusing to install the update, then while that was up go to settings where I could see it in my apps and uninstall it. Then I just installed it again, DLed the boot image, had magisk patch it, flashed it. The image and instructions are around here somewhere.

Was able to uninstall manager by using settings>apps but still cannot install magiskmanager and reroot attempt still no good. Still stuck.

Try flashing Magisk Uninstaller

veatesia said:
Try flashing Magisk Uninstaller
Click to expand...
Click to collapse
No dice.
And originally I did.
Flashed Magisk uninstaller
Flashed OOS update
Flashed TWRP
Rebooted
Flashed Magisk....
No love
I did retry the Magisk uninstaller zip again since you brought it up...but no.
I've even tried the TWRP terminal Magisk module uninstaller to see what is there....only shows Magisk 18.1....which is only sort of there....

The Magisk Manager app must be installed separately from Magisk itself. The zip file does not install the app.

GroovyGeek said:
The Magisk Manager app must be installed separately from Magisk itself. The zip file does not install the app.
Click to expand...
Click to collapse
The apk install fails.
The .zip flash to root appears to work...but not allowing access to system

naxalite971 said:
The apk install fails.
The .zip flash to root appears to work...but not allowing access to system
Click to expand...
Click to collapse
Resolved.
Backed up everything, did a factory reset
Booted via TWRP .img, reran 9.0.12 .zip via sideload,
Reinstalled TWRP
Rebooted into system
Rebooted into recovery
Installed magisk 18.1
Good to go.

Help with installing Magisk on Verizon Samsung Galaxy Note 3 SM-N900V

I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?

jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.

cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.

please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager

@cssr any other input or suggestions?

jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.

cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(

@cssr should i try another version of magisk?

jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?

cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?

What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.

I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.

No certification of play protect

Dear comunity,
I really need your help with this. I have a OP6T and finally updated to the android 11. Before the update, I removed magisk (it was giving me some errors from time to time and I wasn't using the root for anything) through TWRP and then I just updated to the latest OOS through OTA. Everything went smoothly until today, when I went to a store and tried to pay using google pay an error appeared and it seems I have no longer the device certified by the play protect.
What did I miss during the update? Is there any workaround?
Thank you in advance!

I would try wiping and installing the latest oos through twrp instead of ota

I just did this to have everything stock again. Since I installed via OTA, didn't I loose the twrp recovery? Wiping are you referring to a complete clean install? I'm not quite prepared for that :|

igoigo said:
I just did this to have everything stock again. Since I installed via OTA, didn't I loose the twrp recovery? Wiping are you referring to a complete clean install? I'm not quite prepared for that :|
Click to expand...
Click to collapse
I don't understand why it would not be certified after ota update. You can try uninstalling updates for play services and play store maybe that will help. Or there might be magisk files that persisted. Could try to root with magisk again and uninstall it using the magisk app. Just ideas for ya cause I really don't know for sure. But I do know for sure even with stock oos you can still boot a twrp and use it even if you dont make it permanent. So you could use twrp to delete magisk or anything that would be throwing off the safety net. Could also try a safety net checking app to narrow down the problem depending if it passes or not. I just suggested clean install because there may be conflicting device names or whatever from going from custom to ota update. Hope it helps

Brettroth said:
I don't understand why it would not be certified after ota update. You can try uninstalling updates for play services and play store maybe that will help. Or there might be magisk files that persisted. Could try to root with magisk again and uninstall it using the magisk app. Just ideas for ya cause I really don't know for sure. But I do know for sure even with stock oos you can still boot a twrp and use it even if you dont make it permanent. So you could use twrp to delete magisk or anything that would be throwing off the safety net. Could also try a safety net checking app to narrow down the problem depending if it passes or not. I just suggested clean install because there may be conflicting device names or whatever from going from custom to ota update. Hope it helps
Click to expand...
Click to collapse
Thank you for the suggestions. I installed root checker and it didn't detect any root. I was thinking on installing again TWRP to then install/uninstall magisk. But I can try to check the safety net, its strange indeed, I have everything working without any problems, even the google or bank apps.
When I uninstalled magisk I had to do it through TWRP because my magisk manager that was in "hide mode" woulnd't open because it was constantly crashing. As you said, probably there is some remnant files from magisk left.
EDIT: I run the safety checker and it found a problem with "CTS profile matched", any idea what is this?

igoigo said:
Thank you for the suggestions. I installed root checker and it didn't detect any root. I was thinking on installing again TWRP to then install/uninstall magisk. But I can try to check the safety net, its strange indeed, I have everything working without any problems, even the google or bank apps.
When I uninstalled magisk I had to do it through TWRP because my magisk manager that was in "hide mode" woulnd't open because it was constantly crashing. As you said, probably there is some remnant files from magisk left.
EDIT: I run the safety checker and it found a problem with "CTS profile matched", any idea what is this?
Click to expand...
Click to collapse
Basically has 2 different ID's probably from going custom to ota update. That's why I suggested clean install. Anytime going from one rom to another clean install is needed.

@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :|

igoigo said:
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :|
Click to expand...
Click to collapse
Sorry I thought you were on custom

igoigo said:
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :
Click to expand...
Click to collapse
You should be able to just dirty flash the oos from twrp then. Should fix any mismatched id's

I will try the dirty flash through twrp

Brettroth said:
You should be able to just dirty flash the oos from twrp then. Should fix any mismatched id's
Click to expand...
Click to collapse
Finally got some time during my holidays to try this, but now I'm facing some problems. I tried to fastboot flash the TWRP version that you suggested in another thread but the recovery can't read my storage due to encryption. Do you have any suggestion?

igoigo said:
Finally got some time during my holidays to try this, but now I'm facing some problems. I tried to fastboot flash the TWRP version that you suggested in another thread but the recovery can't read my storage due to encryption. Do you have any suggestion?
Click to expand...
Click to collapse
This will decrypt android 12

Brettroth said:
This will decrypt android 12
Click to expand...
Click to collapse
But I'm with in Android 11 stock ROM (11.1.2.2) will it work?

igoigo said:
But I'm with in Android 11 stock ROM (11.1.2.2) will it work?
Click to expand...
Click to collapse
Yeah it should. The other twrp should have worked also with a11. You might have corrupted your data. Probably need to wipe data by typing yes to fix.

How can I have corrupted my data by just flashing the recovery? Can't I flash the stock boot.img?
EDIT:
I was able to flash the stock boot.img and everything is working now. Starting again, what do you suggest, boot TWRP and then instal zip and flash OOS+TWRP? My problem is, which TWRP version should I boot and flash, since the one I tested gave this problem.

Hi, my case is a bit different as i havent used magisk and i have a difderent phone, but my solution to "device is not play store certified" which was showing in play store, about section was as follows:
Enable Developper mode (setting/about/software info/click 7 times or so on "build number")
A developer menu appears in settings at the bottom, within it i disabled "OEM Unlocking".
Restarted phone checked, was still not certified, cleared data for "google play services" and "google play store", restarted, and voila.
Hope it helps