fix magisk safetynet api error

Fix Magisk Safetynet API Error: Detailed Guide

In this guide, we will show you the steps to fix the Magisk Safetynet API error. While rooting a device does bring in a plethora of goodies, on the flip side it has its fair share of disadvantages as well. Right there at the top is the issue of the safetynet flag getting triggered. When that happens, the failure of basicIntegrity check and cts profile mismatch error are two common phenomena.

In simpler words, it would then lead to your inability to run banking and monetary-related apps as well as games like Pokemon Go among others. In this regard, new methods keep on coming that aids in bypassing these security checks. And as of now as well, there is a working method available. But before you actually try it out, you would have to first check if the Safetynet issue is actually there on your device or not.

That could pretty easily be carried out right from the Magisk Manager itself (or the Magisk App, as is now known as beginning with version 22). However, some users are facing an API issue while carrying out this task. If you are also getting bugged with the Magisk Safetynet API error, then this guide shall help you fix it. Follow along.



How to Fix Magisk Safetynet API Error

fix magisk safetynet api error

The below instructions are listed under separate sections for ease of understanding. Make sure to follow in the exact same sequence as mentioned. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.

STEP 1: Switch to Magisk Canary

First and foremost, it is recommended that you switch to the Canary build of Magisk. This is a testing build of Magisk and might be a little bit unstable (though I haven’t experienced anything as such). So refer to the below steps to make this switch right away:

change-magisk-update-channel-canary-fix-safetynet-api-error

  1. Launch the Magisk App
  2. tap on the Settings icon situated at the top right.
  3. Then go to the Update Channel section
  4. Finally, select Canary from the list.

That’s it. In most cases, this is enough to fix the Magisk Safetynet API error. If that doesn’t happen with you, then please proceed with the other steps given below.

STEP 2: Ensure Magisk App Updation

It has been a general notion that users don’t tend to update the Magisk app since it is already providing administrative privileges well as good. However, that is not usually the case, and using an older build could well lead to compatibility issues as well. So it is recommended that you update to the latest version right away.

update magisk fix safetynet api error

For that, launch the Magisk App and if you see an Update button next to App, tap on it and do so right away. If you are already on the latest build, well and good. let’s now move over to the next step to fix the Magisk Safetynet API error.

STEP 3: Delete Magisk Data

Next up, you will have to delete the app data and cache as well. Here’s how it could be carried out:

delete magisk data fix safetynet api error

  1. Head over to the Settings page on your device.
  2. Then go to Apps and Notifications > App Info.
  3. Scroll to the magisk app and go to its Storage and Cache section.
  4. Within that, tap on the Clear Storage/Clear Data option and wait for the process to complete.

STEP 4: Re-Download Magisk SafetyNet API

download magisk Proprietary Code fix safetynet api error

  1. Connect your device to the internet.
  2. Launch the Magisk App and tap on Check SafetyNet.
  3. Magisk will now ask to download the Proprietary Code, tap OK.
  4. Once downloaded, the SafetyNet test result will be right in front of you.

That’s it. These were the steps to fix the Magisk Safetynet API error. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution at the earliest.

About Chief Editor

4 thoughts on “Fix Magisk Safetynet API Error: Detailed Guide”

    1. Sadique Hassan

      Hi Nexon, could you try changing the update channel to Canary. Some users were able to achieve success after doing so. I’m updating the guide with the instructions for the same.

  1. The steps don’t work on OnePuls 7T and Magisk 23 for some reason. There is no Canary update channel either, only Stable, Beta and Custom

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.