Magisk SafetyNet API Error - Galaxy Note 3 Q&A, Help & Troubleshooting

So I was going well, Install TWRP, Take a Nandroid backup, switch from SuperSU to Magisk
But then when I check SafetyNet and click yes on download propeitary code, It wouldn't work. It kept saying "SafetyNet API Error" over and over. I tried:
-Clearing Data and Cache
-Clearing Dalvik Cache.
-Reflash Magisk.
It wouldn't work, Any help?
SM-N900 5.0 Magisk Root with TWRP Recovery

Northgical said:
So I was going well, Install TWRP, Take a Nandroid backup, switch from SuperSU to Magisk
But then when I check SafetyNet and click yes on download propeitary code, It wouldn't work. It kept saying "SafetyNet API Error" over and over. I tried:
-Clearing Data and Cache
-Clearing Dalvik Cache.
-Reflash Magisk.
It wouldn't work, Any help?
SM-N900 5.0 Magisk Root with TWRP Recovery
Click to expand...
Click to collapse
If you have xposed installed, remove it. And try again.
Or just clean magisk manager app data, and open it with internet connection.

I never installed Xposed
I tried it. It didn't work

Related

[G900P] "Unfortunately, System UI has stopped" after installing xposed framework

[G900P] "Unfortunately, System UI has stopped" after installing xposed framework
I recently installed the MOAR rom on my 5.0 G900P since the rom is deodexed and to install xposed, you need a deodexed phone. I flashed the xposed-v75-sdk21-arm-arter97-snapdragon.zip from http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463 and when I reboot my phone, I get the error (did I install the wrong zip file?). I've tried clearing the dalvik cache and cache partition (I get an error when trying to clear the cache partition), and none of these have worked. Is there anything I can do to fix this, or should I just not install xposed? Thanks.
EDIT: I flashed the uninstaller provided by rovo89, but I still am having the same problem. I also get the error "Unfortunately, the process android.process.acore has stopped."
kevinm614 said:
I recently installed the MOAR rom on my 5.0 G900P since the rom is deodexed and to install xposed, you need a deodexed phone. I flashed the xposed-v75-sdk21-arm-arter97-snapdragon.zip from http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463 and when I reboot my phone, I get the error (did I install the wrong zip file?). I've tried clearing the dalvik cache and cache partition (I get an error when trying to clear the cache partition), and none of these have worked. Is there anything I can do to fix this, or should I just not install xposed? Thanks.
EDIT: I flashed the uninstaller provided by rovo89, but I still am having the same problem. I also get the error "Unfortunately, the process android.process.acore has stopped."
Click to expand...
Click to collapse
Reinstall the same rom without wiping data or cache it will definitely work bro

Cannot install magisk v12.0[SOLVED]

So I installed magisk v12 via normal procedure; downloaded then installed from recovery, and the phone didn't boot after. Did not even get past the samsung j5 logo to the bootanimation. I've tried uninstalling SuperSu and then install magisk but didn't help. I "updated" the same rom I was using already and I can use my phone but I would like to install magisk. Anyone?
Phone:J500FN (2015)
Rom: Resurrection remix 5.8.3
Weird, never had problems installing Magisk, even on secondary roms (multirom) when all other fail.
Wipe system, and install the ROM then Magisk, in case that doesn't work make a clean install (wipe system, data, dalvik, cache) and install only the ROM and Magisk (no gapps), if everything is working then install gapps the rest (apps, restore backups etc...)
Your Magisk could be corrupted, try download again and install.
American_Jesus said:
Weird, never had problems installing Magisk, even on secondary roms (multirom) when all other fail.
Wipe system, and install the ROM then Magisk, in case that doesn't work make a clean install (wipe system, data, dalvik, cache) and install only the ROM and Magisk (no gapps), if everything is working then install gapps the rest (apps, restore backups etc...)
Your Magisk could be corrupted, try download again and install.
Click to expand...
Click to collapse
Wiping system will have no effect. Magisk nor supersu Install anything to system.
Restore the untouched boot.img then install Magisk only.
That should be all that is required.
ashyx said:
Wiping system will have no effect. Magisk nor supersu Install anything to system.
Restore the untouched boot.img then install Magisk only.
That should be all that is required.
Click to expand...
Click to collapse
I said to wipe system in case of something installed on system before causing the bootloop (BusyBox, viper4android, etc...). Wasn't referring to Magisk or SuperSu.
That's way I said to install Magisk before gapps, to leave system untouched so it can diagnose the problem.
American_Jesus said:
I said to wipe system in case of something installed on system before causing the bootloop (BusyBox, viper4android, etc...). Wasn't referring to Magisk or SuperSu.
That's way I said to install Magisk before gapps, to leave system untouched so it can diagnose the problem.
Click to expand...
Click to collapse
Well considering he stated that it wouldn't boot directly after installing Magisk, we can deduce that it was likely Magisk that caused the issue.
ashyx said:
Well considering he stated that it wouldn't boot directly after installing Magisk, we can deduce that it was likely Magisk that caused the issue.
Click to expand...
Click to collapse
I can't deduce anything, that's way I recommend to remove any modifications before install.
If you want to debug a problem start removing the variants.
Thanks guys! Problem solved. System wipe didn't do it. It was easier for me to clean install than restore the boot.img at the moment so that fixed it this time. Thank you again. ???

Issue upgrading from oxygenos 4.5.14 to 5.0.2 on formerly rooted device

I have a formerly rooted OP 5 currently running oxygenos 4.5.14(this was dirty flashed from a rooted 4.5.3 device) and wanted to upgrade to 5.0.2 without losing my data. I have lost the root and that's fine. I am trying to upgrade to 5.0.1 or 5.0.2 and the update keeps failing. Anyone have tips or guidance on how to proceed?
unless you relock your bootloader you won't be able to update. i tried everything. make sure you backup your data before you relock bootloader beacause this process will wipe everything.
cmd code to lock bootloader - fastboot oem lock
alternatively you can try this but i haven't tried so i won't recommend this method - https://forum.xda-developers.com/oneplus-5/how-to/guide-upgrade-nougat-rooted-encrypted-t3734779
patel lav said:
unless you relock your bootloader you won't be able to update. i tried everything. make sure you backup your data before you relock bootloader beacause this process will wipe everything.
cmd code to lock bootloader - fastboot oem lock
alternatively you can try this but i haven't tried so i won't recommend this method - https://forum.xda-developers.com/oneplus-5/how-to/guide-upgrade-nougat-rooted-encrypted-t3734779
Click to expand...
Click to collapse
would you recommend this if I just follow this tutorial up to step 8? I'm on 4.5.14 and would like to update to 5.0.2 even I lose my data and internal storage.
Step
Always succeed to upgrade in my case and not losing any data, maybe my way can help you
1. Instal codeworkx twrp not bluspark twrp, if you already have codeworkx just ignore this step
2. Wipe dalvik and cache
3. Instal update (full zip not partial zip)
4. Wipe dalvik and cache again
5. If you want to root, instal magisk 15.2 (recommended) and if you don't just ignore this step and reboot
6. Wipe dalvik and cache again (last time)
7. Reboot and enjoy your update
lazygeniuslanz said:
would you recommend this if I just follow this tutorial up to step 8? I'm on 4.5.14 and would like to update to 5.0.2 even I lose my data and internal storage.
Click to expand...
Click to collapse
i haven't tried this method but if you still wanna try this you can dig into this.
brototo31 said:
Always succeed to upgrade in my case and not losing any data, maybe my way can help you
1. Instal codeworkx twrp not bluspark twrp, if you already have codeworkx just ignore this step
2. Wipe dalvik and cache
3. Instal update (full zip not partial zip)
4. Wipe dalvik and cache again
5. If you want to root, instal magisk 15.2 (recommended) and if you don't just ignore this step and reboot
6. Wipe dalvik and cache again (last time)
7. Reboot and enjoy your update
Click to expand...
Click to collapse
To elaborate some of these steps:
1. Boot to fastloader and install codeworx twrp
2. Boot to twrp (codeworx) then wipe dalvik and cache
3. Flash the signed zip (5.0.2)
4. Wipe dalvik cache
5. Install magisk zip
6. Wipe dalvik cache
7. Boot to system
Is this right? What should I do if I have xposed modules and magisk modules currently?
patel lav said:
i haven't tried this method but if you still wanna try this you can dig into this.
Click to expand...
Click to collapse
Thank you!
brototo31 said:
Always succeed to upgrade in my case and not losing any data, maybe my way can help you
1. Instal codeworkx twrp not bluspark twrp, if you already have codeworkx just ignore this step
2. Wipe dalvik and cache
3. Instal update (full zip not partial zip)
4. Wipe dalvik and cache again
5. If you want to root, instal magisk 15.2 (recommended) and if you don't just ignore this step and reboot
6. Wipe dalvik and cache again (last time)
7. Reboot and enjoy your update
Click to expand...
Click to collapse
Although this will get me to the most recent update i will continue to run into update issues unless my bootloader is relocked right?

Oneplus 5 shutting down after the OTA

Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Dr4In said:
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Click to expand...
Click to collapse
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
strongst said:
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
Click to expand...
Click to collapse
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Dr4In said:
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Click to expand...
Click to collapse
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
strongst said:
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
Click to expand...
Click to collapse
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Dr4In said:
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Click to expand...
Click to collapse
If you mean your encrypted twrp of your internal storage = no.
I would start from scratch with decrypted.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I used this and solved the problem
I was facing to the same problem today, and the problem was the Magisk version! Same problem for Pixel 3/XL users...
The way you can fix it: Install v19.1 BETA (not the stable)! It should boot up!

Camera failure when booting into Magisk

Hi
My S10+ exynos started behaving strangely: apps crashing, camera failure etc.
Android 10, Magisk 20.4
So I did a factory reset. This indeed fixed the app problem. However, the camera failure still is present. Once booted into regular system, it works flawlessly. When booted in Magisk, there is a black screen and then the message "warning: camera failure". Other camera apps don't work as well.
I did a search here and tried:
Solving safety net cts problem. This is fixed, but didn't solve the camera problem.
Fixed permissions with built prop editor to rw-r-r. Didn't work either.
Of course I deleted cache/data from camera, wiped cache/dalvik in TWRP, went to safe mode with no success
Installed Magisk modules:
Busybox for android ndk
Magisk hide props config
Systemless host
To my best knowledge, I didn't change the configuration before the camera problem appeared.
I am running out of ideas. So please help me. Thanks in advance!
SOLVE: I forgot, I updated TWRP and in my case the TWRP Kernel and system didn't match. I did a
restore of my initial backup in TWRP
flash latest firmware and booted
patched AP file in magisk and flashed this via Odin (follow the stets when installing Magisk)
patched TWRP (used the IanMcd version) and flashed (follow the guide on how to flash TWRP)
Once the system booted I I restored all apps from my TB backup.

Categories

Resources