Related
Hi
I'm using a Samsung Galaxy S4
I rooted the stock Samsung rom with SuperSU prior to install Magisk
At first I couldn't install 13.3 I had to install 12.0 because of some unknown reason installing 13.3 I got the error image mount failed same with all previous 13. versions however now 13.3 is now installed and SuperSU isn't installed.
When I run the SafetyNet Check in Magisk it reports:
ctsProfile: false
basicIntegrity: false
I want to be able to use apps like Android pay and such
Can someone please help me with getting this to work
Thanks!
Magisk v12.0 can't pass SafetyNet without workarounds like Universal SafetyNet fix module (and since the last update to SafetyNet a few days ago I've no idea if that works either).
You can't use Magisk to pass SafetyNet with SuperSU installed.
Here's some reading for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Pro tip: Try using the search function and browse the stickied threads before posting. There are very few things that hasn't been covered already in one way or another...
Didgeridoohan said:
Magisk v12.0 can't pass SafetyNet without workarounds like Universal SafetyNet fix module (and since the last update to SafetyNet a few days ago I've no idea if that works either).
You can't use Magisk to pass SafetyNet with SuperSU installed.
Here's some reading for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Pro tip: Try using the search function and browse the stickied threads before posting. There are very few things that hasn't been covered already in one way or another...
Click to expand...
Click to collapse
I've got 13.3 installed and SuperSU isn't installed plus I've already read a lot on this subject and most of my searches did nothing for me that's why I thought I would make a thread to see if anyone could help me.
AyanamiRei0 said:
I've got 13.3 installed and SuperSU isn't installed plus I've already read a lot on this subject and most of my searches did nothing for me that's why I thought I would make a thread to see if anyone could help me.
Click to expand...
Click to collapse
That was not very clear from your first post...
If you haven't already, start by reading through the link I posted. You wan't post #4.
Didgeridoohan said:
That was not very clear from your first post...
If you haven't already, start by reading through the link I posted. You wan't post #4.
Click to expand...
Click to collapse
Interesting trying to start magiskhide manually does nothing.
You could have remnants of Su on your phone. Even if you use the full uninstall method you can have leftovers. Tried a complete fresh reinstall?
phuhcue said:
You could have remnants of Su on your phone. Even if you use the full uninstall method you can have leftovers. Tried a complete fresh reinstall?
Click to expand...
Click to collapse
Oh it's working fine now installing Lineage OS and then install Magisk and it works perfectly.
With me my experiments with magisk in the past left some files in my data partition behind which makes safetynet fail.
I found them by going into twrp recovery, starting and adb shell and then executing find . | grep -i magisk
the two files i found were:
data/data/com.google.android.gms/files/backup_diff_script/com.topjohnwu.magisk
data/property/persist.magisk.hide
i deleted them with rm and safety net worked again.
So I can confirm that for my phone, unlocked bootloader, custom modem and custom recovery does not matter at all. But if your filesystem still contains traces of magisk, is a nono for google safetynet, pretty silly this road they are taking here.
safety net
i have the same problem on galaxy note 3 with magisk 15.3 on my galaxy s7 everything is ok but in note 3 i have safety net false...
can anyone help me?
spanpana said:
i have the same problem on galaxy note 3 with magisk 15.3 on my galaxy s7 everything is ok but in note 3 i have safety net false...
can anyone help me?
Click to expand...
Click to collapse
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Didgeridoohan said:
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Click to expand...
Click to collapse
thank's for your reply...!
i have custom rom resurection remix v.5.8.2 but i didnt change the kernel can you explain me how to do that please because i don't know...?
spanpana said:
thank's for your reply...!
i have custom rom resurection remix v.5.8.2 but i didnt change the kernel can you explain me how to do that please because i don't know...?
Click to expand...
Click to collapse
Check your kernel version first (usually found in Settings - About Phone). If it's less than 3.8, ask for help in your device's forum for if there's any custom kernels or ROMs available with an updated kernel.
Didgeridoohan said:
Check your kernel version first (usually found in Settings - About Phone). If it's less than 3.8, ask for help in your device's forum for if there's any custom kernels or ROMs available with an updated kernel.
Click to expand...
Click to collapse
ok my friend thank you very much...!:laugh::good:
Didgeridoohan said:
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Click to expand...
Click to collapse
That's interesting. I get the same message on my old phone (running the 3.4.113 kernel), but I'm unable to even open Mario Run if MagiskHide is disabled. But when it's enabled, the game runs just fine. Is that normal? I thought Mario Run made use of SafetyNet... I'm using microG + DroidGuard Helper. I've tried running Android Pay, but I get this error message. But I'm not even sure if Android Pay is supposed to work since I'm using microG... What other apps use SafetyNet so I can try them?
Thanks.
robotsrules said:
That's interesting. I get the same message on my old phone (running the 3.4.113 kernel), but I'm unable to even open Mario Run if MagiskHide is disabled. But when it's enabled, the game runs just fine. Is that normal? I thought Mario Run made use of SafetyNet... I'm using microG + DroidGuard Helper. I've tried running Android Pay, but I get this error message. But I'm not even sure if Android Pay is supposed to work since I'm using microG... What other apps use SafetyNet so I can try them?
Thanks.
Click to expand...
Click to collapse
MagiskHide can't do it's thing to hide itself on such an old kernel, but it can still hide sensitive prop values. That's why Mario Run works... IIRC it looks for ro.debuggable, on of the props changed to "safe" values by MagiskHide.
Didgeridoohan said:
MagiskHide can't do it's thing to hide itself on such an old kernel, but it can still hide sensitive prop values. That's why Mario Run works... IIRC it looks for ro.debuggable, on of the props changed to "safe" values by MagiskHide.
Click to expand...
Click to collapse
Oh, I get it now... Thanks
Hi, I have a problem with my OnePlus 2. My phone is running Lineage OS 14.1 and I can't play Pokemon go. My phone has been rooted but I uninstalled it so Pokemon should work right? I also did a safetynet check and I didn't pass it. I hope anyone here can help me with this.
michiel.dj said:
Hi, I have a problem with my OnePlus 2. My phone is running Lineage OS 14.1 and I can't play Pokemon go. My phone has been rooted but I uninstalled it so Pokemon should work right? I also did a safetynet check and I didn't pass it. I hope anyone here can help me with this.
Click to expand...
Click to collapse
You need a factory reset, probably.
NLBeev said:
You need a factory reset, probably.
Click to expand...
Click to collapse
Thanks I'll try it
Apart from root, there are also other things that trigger SafetyNet. Most common suspects:
Bootloader needs to be locked or you'll need something that masks/doesn't report the bootloader state. Some custom kernels do this.
SELinux need to be enforcing.
Thanks, is it possible to lock the bootloader again?
michiel.dj said:
Thanks, is it possible to lock the bootloader again?
Click to expand...
Click to collapse
The OnePlus Two does not report bootloader lock status to SafetyNet so it does not matter if it is unlocked.
I would try reflashing the rom and making sure it is not rooted. If you want root you will want to flash Magisk via TWRP.
driverdis said:
The OnePlus Two does not report bootloader lock status to SafetyNet so it does not matter if it is unlocked.
I would try reflashing the rom and making sure it is not rooted. If you want root you will want to flash Magisk via TWRP.
Click to expand...
Click to collapse
Thank you, I will try to reflash it and see if it is working. I'm sure my phone is not rooted anymore, I have uninstalled the root in the SuperSU app.
michiel.dj said:
Thank you, I will try to reflash it and see if it is working. I'm sure my phone is not rooted anymore, I have uninstalled the root in the SuperSU app.
Click to expand...
Click to collapse
I reflashed the ROM and everthing is working fine now. But my camera is a little laggy. But that is not something to talk about in this thread. Thank you guys for helping me with my problem
Good day all
Will xposed work on Note 8 (N950FD)?
Thanks in advance
I would guess that an installer for an S8+ might work since it is basically the same device. Since rooting with TWRP and SuperSU I've flashed a few things meant for S8 devices and they either work properly as is or with very minor script tweaking.
Kalm_Traveler said:
I would guess that an installer for an S8+ might work since it is basically the same device. Since rooting with TWRP and SuperSU I've flashed a few things meant for S8 devices and they either work properly as is or with very minor script tweaking.
Click to expand...
Click to collapse
Thanks alot for your quick and kind reply...
Yes it worked... Issue is closed
how are you guys gaining root access?
Hdhntr23 said:
how are you guys gaining root access?
Click to expand...
Click to collapse
Exynos models had root several days ago. I'm using SuperSU at the moment.
me7tarfeek said:
Yes it worked... Issue is closed
Click to expand...
Click to collapse
نوّرنا الله يرضى عليك.
We are here to learn, share and contribute. Otherwise, only the development section would be active (thanks to the developers) while the rest of the sections would be full of threads asking for help.
What method for root did you go with? URL for guide page?
What Xposed modules have you tried and are working? root cloak? Snapprefs?
Did you pass SafteyNet?
Thanks in advance.
Hello with xposed what stuff is actually working and is it stable at all for daily use please?
Kalm_Traveler said:
Exynos models had root several days ago. I'm using SuperSU at the moment.
Click to expand...
Click to collapse
Does Samsung Pay work?
طوني تبولة said:
نوّرنا الله يرضى عليك.
We are here to learn, share and contribute. Otherwise, only the development section would be active (thanks to the developers) while the rest of the sections would be full of threads asking for help.
What method for root did you go with? URL for guide page?
What Xposed modules have you tried and are working? root cloak? Snapprefs?
Did you pass SafteyNet?
Thanks in advance.
Click to expand...
Click to collapse
Sure will do
I root with Magisk 14.0 with SafeNet pass
Follow this https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-8-exynos-t3674036
Flashed 26-07-17-xposed-v87-sdk25-Xposed-by-PurifyOS.zip
Now I use the following modules in the image
SiNJiN76 said:
Does Samsung Pay work?
Click to expand...
Click to collapse
I don't think it ever works with a different country device, or on a rooted phone.
me7tarfeek said:
Sure will do
I root with Magisk 14.0 with SafeNet pass
Follow this https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-8-exynos-t3674036
Flashed 26-07-17-xposed-v87-sdk25-Xposed-by-PurifyOS.zip
Now I use the following modules in the image
Click to expand...
Click to collapse
This and Magisk exposed module—that's all to install Xposed?
Are you experiencing some instability—some apps FCing sometimes, or nothing at all?
白い熊 said:
This and Magisk exposed module—that's all to install Xposed?
Are you experiencing some instability—some apps FCing sometimes, or nothing at all?
Click to expand...
Click to collapse
I did not install Magisk xposed module.. I used the normal stand alone xposed... It worked perfect with no issues at all. My device is N950FD....
Hdhntr23 said:
how are you guys gaining root access?
Click to expand...
Click to collapse
Follow this link if your device is N950F/FD....
https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-8-exynos-t3674036
Kalm_Traveler said:
Exynos models had root several days ago. I'm using SuperSU at the moment.
Click to expand...
Click to collapse
Is lacky patcher working with super su ?
me7tarfeek said:
I did not install Magisk xposed module.. I used the normal stand alone xposed... It worked perfect with no issues at all. My device is N950FD....
Click to expand...
Click to collapse
Which root do you have—SuperSU or Magisk? I have Magisk, so tried with 26-07-17-xposed-systemless-v87-sdk25-by-PurifyOS.zip but that throws me into a bootloop directly?
How did you proceed chronologically?
First the Xposed apk (which one?), then flash the Purify zip? Did you wipe anything before or after, data or cache? I've read many conflicting reports, since you've done it should be possible to replicate it…
白い熊 said:
Which root do you have—SuperSU or Magisk? I have Magisk, so tried with 26-07-17-xposed-systemless-v87-sdk25-by-PurifyOS.zip but that throws me into a bootloop directly?
How did you proceed chronologically?
First the Xposed apk (which one?), then flash the Purify zip? Did you wipe anything before or after, data or cache? I've read many conflicting reports, since you've done it should be possible to replicate it…
Click to expand...
Click to collapse
I flashed Magisk 14 root... Restarted the device to check root... Then Installed xposed apk (XposedInstaller_by_dvdandroid_09_09_17)... Then flashed the above xposed framework. Restarted the device to check xposed, then installed modules...
No wipe at all... The device restarted normaly with no issue..
Good luck
me7tarfeek said:
I flashed Magisk 14 root... Restarted the device to check root... Then Installed xposed apk (XposedInstaller_by_dvdandroid_09_09_17)... Then flashed the above xposed framework. Restarted the device to check xposed, then installed modules...
No wipe at all... The device restarted normaly with no issue..
Good luck
Click to expand...
Click to collapse
Does this break Android Pay?
vinokirk said:
Does this break Android Pay?
Click to expand...
Click to collapse
I think so. As far as I know, root breaks Android Pay.
We do not have it here so I can not be sure...
Hey guys,
Trying to install the systemless XPosed for Nougat on my Note 8, but for some reason, after installation, it stops my 256GB Exynos Note 8 from booting up. Was able to recover it by running the Magisk uninstaller via TWRP.
Noticed that on the official XPosed thread, it states that it'll 'cause boot loop issues on stock Samsung ROM, but on the Systemless XPosed Page, it claims the SDK 24 and 25 are universal, so, what's wrong?
Any suggestions on getting systemless XPosed working on my Exynos Note 8 with Nougat? I especially want the systemless variant as it allows easy on/off whenever I'm going shopping and want to use Android Pay instead of having to uninstall all modules.
Hi,
It's a long time that I don't use root on my Oneplus 3T.
What I want to know is that if with the latest Oxygen Os, unlocked bootloader and latest magisk root / magisk hide I will be able to use Google Pay.
I know that Google can update SafetyNet detection algorithm, so usually if that happens after how long Magisk is updated to hide root again?
Thanks!
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
tetra96 said:
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
Click to expand...
Click to collapse
Without hiding the status of the bootloader, for sure Google Pay won't work. But Magisk Hide, can hide root status and bootloader status.
That's what I want to know, if Magisk Hide working or not
Waiting more responses from other users
andQlimax said:
Without hiding the status of the bootloader, for sure Google Pay won't work. But Magisk Hide, can hide root status and bootloader status.
That's what I want to know, if Magisk Hide working or not
Waiting more responses from other users
Click to expand...
Click to collapse
Google Pay works fine with Magisk. You don't need to hide it or hide Magisk Manager.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Google Pay works fine with Magisk. You don't need to hide it or hide Magisk Manager.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Can you explain how you were able to make it work? Because whether I hide Google Pay in Magisk or not, when I try to setup my credit card in Google Pay it says "Couldn't finish setup to pay in shops. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I have a OnePlus 3 Oxygen 5.0.6 and Android 8.0.0 with Magisk 17.1.
axelryder said:
Can you explain how you were able to make it work? Because whether I hide Google Pay in Magisk or not, when I try to setup my credit card in Google Pay it says "Couldn't finish setup to pay in shops. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I have a OnePlus 3 Oxygen 5.0.6 and Android 8.0.0 with Magisk 17.1.
Click to expand...
Click to collapse
That's odd. I didn't have to do anything to get it working. I'm on OOS 5.0.5 and Magisk 17.1.
Two question: is your phone encrypted and do you have a pin/password set?
My phone is encrypted and I use a password.
You could also try hiding Magisk Manager (I haven't needed to do this) and delete any Magisk folder on you internal storage.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That's odd. I didn't have to do anything to get it working. I'm on OOS 5.0.5 and Magisk 17.1.
Two question: is your phone encrypted and do you have a pin/password set?
My phone is encrypted and I use a password.
You could also try hiding Magisk Manager (I haven't needed to do this) and delete any Magisk folder on you internal storage.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I have a pin set, I don't think my phone is encrypted; although when I go to the Security menu, under "Encryption" it does say "Encrypted", but I don't remember setting it up. So I guess it is!
I did try to hide Magisk Manager from their option in the settings menu, but I still got the same error in Google Pay after;
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
axelryder said:
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
Click to expand...
Click to collapse
Yes; SafetyNet check means that app contacted with Google server with success, but the result of your device check is false, which means that your device is not certified "secure" in its current state.
Perhaps you tampered system partition?
tetra96 said:
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
Click to expand...
Click to collapse
Did you try with a custom kernel? Your kernel needs SultanXDA's patch to pass safetynet with a unlocked bootloader. There is a magisk module here, that might work if you don't want a custom kernel. There's also some commands you can run on your devices terminal here, that might work too. I only have experience with using a custom kernel but the changelog for the module does say it was patched for OP3 support.
axelryder said:
...
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
Click to expand...
Click to collapse
You've definitely installed something that breaks SafetyNet. Xposed used to do this, though I think it's been fixed to work with Magisk.
namanjr said:
Did you try with a custom kernel? Your kernel needs SultanXDA's patch to pass safetynet with a unlocked bootloader. There is a magisk module here, that might work if you don't want a custom kernel. There's also some commands you can run on your devices terminal here, that might work too. I only have experience with using a custom kernel but the changelog for the module does say it was patched for OP3 support.
Click to expand...
Click to collapse
Both Magisk and custom kernels patch the boot image so that it doesn't trigger dm-verity and pass SafetyNet. You don't need to use a custom kernel if you're using Magisk.
Sent from my OnePlus3T using XDA Labs
My Safetynet check is successful. Yet it doesnt work with Google Pay. I am told that PAY is not supported on my device as it is rooted.
przemcio510 said:
Yes; SafetyNet check means that app contacted with Google server with success, but the result of your device check is false, which means that your device is not certified "secure" in its current state.
Perhaps you tampered system partition?
Click to expand...
Click to collapse
BillGoss said:
You've definitely installed something that breaks SafetyNet. Xposed used to do this, though I think it's been fixed to work with Magisk.
Both Magisk and custom kernels patch the boot image so that it doesn't trigger dm-verity and pass SafetyNet. You don't need to use a custom kernel if you're using Magisk.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I do indeed have Xposed installed, V90 beta 3. I guess maybe it's not fixed for Magisk after all :/
@przemcio510 do you use Xposed ?
axelryder said:
I do indeed have Xposed installed, V90 beta 3. I guess maybe it's not fixed for Magisk after all :/
@przemcio510 do you use Xposed ?
Click to expand...
Click to collapse
Yes, I do, Xposed breaks SafetyNet and there's nothing you can do to keep it installed and have SN passing
przemcio510 said:
Yes, I do, Xposed breaks SafetyNet and there's nothing you can do to keep it installed and have SN passing
Click to expand...
Click to collapse
Oh I see... well here's my problem I guess lol
On my Redmi note 4 From recent update of miui 10 and magisk 17.1 update google pay stopped working even though safety net check is passed. Earlier google pay was working fine.
Is there any work around?
Sahil Shaikh said:
On my Redmi note 4 From recent update of miui 10 and magisk 17.1 update google pay stopped working even though safety net check is passed. Earlier google pay was working fine.
Is there any work around?
Click to expand...
Click to collapse
This is a OnePlus 3T forum. Ask the question in the Redmi forum.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
This is a OnePlus 3T forum. Ask the question in the Redmi forum.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Sahil Shaikh said:
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Click to expand...
Click to collapse
I think that your problem is specific to MiUI, because on our phones it works fine
Sahil Shaikh said:
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Click to expand...
Click to collapse
As per the previous post, Google Pay works just fine with Magisk installed. There's no need to hide it.
Sent from my OnePlus3T using XDA Labs
andQlimax said:
Hi,
It's a long time that I don't use root on my Oneplus 3T.
What I want to know is that if with the latest Oxygen Os, unlocked bootloader and latest magisk root / magisk hide I will be able to use Google Pay.
I know that Google can update SafetyNet detection algorithm, so usually if that happens after how long Magisk is updated to hide root again?
Thanks!
Click to expand...
Click to collapse
It is reliant on safetynet AFAIK, and that passes on my device when using Magisk - havent tried Android Pay as of yet, but am aware that Safetynet passes.
I've fastboot flashed the official stock rom, MIUI EU and others. They all don't pass safetynet the CTS profile mismatch which means my device isn't certified in google play store. Other OSS roms like arrowOS works and passes.
How can I fix it
Found a potential fix here. Testing it in a few. Will update. https://droidholic.com/fix-safetynet-failed-cts-profile-false/
TechV said:
I've fastboot flashed the official stock rom, MIUI EU and others. They all don't pass safetynet the CTS profile mismatch which means my device isn't certified in google play store. Other OSS roms like arrowOS works and passes.
How can I fix it
Click to expand...
Click to collapse
Download and enable "MagiskHide Props Config" module from the magisk modules section. Reboot. The method provided from droidholic did not work for me on Motorola G Power 2021 Boost Mobile USA variant Magisk rooted. Nor did MagiskHide props. However, My play store and certain easily triggered apps still work thanks to the Magisk Hide props module.
DrRoxxo said:
Download and enable "MagiskHide Props Config" module from the magisk modules section. Reboot. The method provided from droidholic did not work for me on Motorola G Power 2021 Boost Mobile USA variant Magisk rooted. Nor did MagiskHide props. However, My play store and certain easily triggered apps still work thanks to the Magisk Hide props module.
Click to expand...
Click to collapse
I don't want to use magisk. My phone can't be rooted because of work related reasons. I flashed the latest fastboot rom and it still doesn't pass CT profile check. My play store says device is not certified.
How can this be?
TechV said:
I don't want to use magisk. My phone can't be rooted because of work related reasons. I flashed the latest fastboot rom and it still doesn't pass CT profile check. My play store says device is not certified.
How can this be?
Click to expand...
Click to collapse
Unlocked bootloader
Why you flash stock without to wanna root, instead only update original fw if it's a company phone?
You can try to lock the bootloader again with miflash but I recommend to read exactly the manuals before locking again.
DrRoxxo said:
Found a potential fix here. Testing it in a few. Will update. https://droidholic.com/fix-safetynet-failed-cts-profile-false/
Click to expand...
Click to collapse
This fix worked for me. Thank you!
Sweet + OctaviOS 2.8
Koerschgen said:
This fix worked for me. Thank you!
Sweet + OctaviOS 2.8
Click to expand...
Click to collapse
I am absolutely ecstatic to hear that!
TechV said:
I don't want to use magisk. My phone can't be rooted because of work related reasons. I flashed the latest fastboot rom and it still doesn't pass CT profile check. My play store says device is not certified.
How can this be?
Click to expand...
Click to collapse
I am no expert, but I do believe once the bootloader is unlocked, it triggers a flag at boot level. It does warn against unlocking the bootloader on most devices prior to unlocking. I'd say that once anything is flashed, another flag is triggered. It's like Knox, but for the boot level I think. If you check the bootloader, there is usually some red and yellow colored text output that helps to diagnose the current state of the device. I am no pro, so I hope this makes sense and provides answers.
DrRoxxo said:
I am no expert, but I do believe once the bootloader is unlocked, it triggers a flag at boot level. It does warn against unlocking the bootloader on most devices prior to unlocking. I'd say that once anything is flashed, another flag is triggered. It's like Knox, but for the boot level I think. If you check the bootloader, there is usually some red and yellow colored text output that helps to diagnose the current state of the device. I am no pro, so I hope this makes sense and provides answers.
Click to expand...
Click to collapse
No unlocked bootloader has nothing to do with it. Google broke safetynet for almost all ROMS starting sep 2 I think. The latest Arrow OS ROM and a few other ROMS that just released new builds pass safetynet once again.
hi
I have A video on it all Necessary information and modules are in a single zip file to pass safety net, follow v the video and pass Safetynet
link here
@TechV did you find a solution to this?