Anyone successful getting tethering on the may update and magisk 16.4? I don't even see that module in the magisk repository anymore. Anyone have any advice, other than modifying build.prio? (Which I tried doing, still can't get it to work!)
Related
Lately it seems more and more developers are relying on safetynet for apps and features (especially google, i REALLY miss getting surveys with opinion rewards :[ )
So I'm curious if anyone has an idea what currently triggers a failed response.
Does busybox fail?
Does selinux need to be enforcing?
Does system status need to be "official"
Etc.
Lastly, bonus question:
Are there any custom kernels for g920p that don't auto root and install busybox?
It is fairly complex.
1) https://developer.android.com/training/safetynet/index.html
"SafetyNet examines software and hardware information on the device where your app is installed to create a profile of that device. The service then attempts to find this same profile within a list of device models that have passed Android compatibility testing. "
2) https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/
"Google uses something called SafetyNet to detect whether your device is rooted or not, and blocks access to those features. Google isn’t the only one, either–plenty of third-party apps also won’t work on rooted Android devices, although they may check for the presence of root in other ways."
You may already know this from the other thread regarding Magisk, but my suggestion is to return to stock via Odin, then follow the instructions from the Magisk thread here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
koop1955 said:
It is fairly complex.
1) https://developer.android.com/training/safetynet/index.html
"SafetyNet examines software and hardware information on the device where your app is installed to create a profile of that device. The service then attempts to find this same profile within a list of device models that have passed Android compatibility testing. "
2) https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/
"Google uses something called SafetyNet to detect whether your device is rooted or not, and blocks access to those features. Google isn’t the only one, either–plenty of third-party apps also won’t work on rooted Android devices, although they may check for the presence of root in other ways."
You may already know this from the other thread regarding Magisk, but my suggestion is to return to stock via Odin, then follow the instructions from the Magisk thread here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks for chiming in!
Dang there's a lot going on, i guess google is being pretty tight lipped about exactly what info they use.
But yea, at the moment I'm completely stock with magisksu and magisk v11.1
The issue is that magisk has to be re-installed after every boot, meaning there are a few minutes where safetynet and gms have the opportunity to see my root before i re-install magisk. (From what i gather from the magisk op thread, this could be fixed with a custom kernel... tested succesfully with skyhigh, but then failed safetynet and i don't know why.)
The other issue with the magisk set-up on complete stock is that Titanium backup and some other root-related apps seem to be almost entirely broken. Magisk OP thread sheds some light about that, something about system needing to mounted as rw (which I'm unable to change, since root hardly works at all)... a couple weeks ago the magisk dev said he was going to work on a fix for that, but I'm not banking on it.
So to summarize, I'm trying to figure out how to run a custom kernel (or even rom if possible) without failing safetynet... because even if i flash skyhigh on stock, Uninstall busybox, set se linux to enforced, uninstall supersu, and wipe davlik i still fail safetynet.
Or I'm i just too greedy wanting the freedom of root AND the comfort of stock behavior? (android pay, google opinion rewards, consistent play service function and updates etc)
I would guess that a custom kernel alone (no SuperSU or BusyBox) would cause a failure. It seems like any kernel mod would do so.
Magisk is an attempt to solve this, but doesn't seem quite there.
koop1955 said:
I would guess that a custom kernel alone (no SuperSU or BusyBox) would cause a failure. It seems like any kernel mod would do so.
Magisk is an attempt to solve this, but doesn't seem quite there.
Click to expand...
Click to collapse
I'd believe that, i guess that'd really be the obvious first step in profiling a device's environment.
Given that I'm guessing it'd just check the system info, all the info on the about device page in settings and compare it to which kernel i should have.
So in the interest of crawling deeper down this rabbit hole, I'm going to see what can be done to mock that info >
Also in defense of magisk, from what i gather, magisk is an extremely effective hands-off root solution... unless you have a samsung device.
@Nye-uhls, you should definitely check this out: https://forum.xda-developers.com/showpost.php?p=71398440&postcount=342
New kernel with built-in Magisk support.
koop1955 said:
@Nye-uhls, you should definitely check this out: https://forum.xda-developers.com/showpost.php?p=71398440&postcount=342
New kernel with built-in Magisk support.
Click to expand...
Click to collapse
Thats huge. I'm officially no longer putting effort into getting magisk working in anticipation of that new kernel.
Thank you for the heads up, probably wouldve kept sweating over this for a few more days lol.
I'm just flashed my phone to the latest LineageOS by jrior with SU Addon, and I realise Im unable to use Android Pay due to SafetyNet.
I've tried installing Magicks that's downloaded from Google PlayStore's Magicks Manager, but it failed and my phone would stuck at TWRP.
I couldn't find Xposed Framework for LineageOS 14.1, I suppose it wasn't out yet?
Is there any ways I could bypass SafetyNet to at least able to use Android Pay?
Thanks in advance guys!
xposed is the problem atm, u can use magisk's su and magisk hide or a few other methods to pass safetynet checks for root but bc exposed directly hooks into the framework there is no current method to bypass xposed detection..
on another note from my experience in the past, not sure if this still applies bc i dont have time needed to research into bypassing it, but when PoGo was first starting to use safetynet i noticed then that the google services framework runs a check on the device for then sends it to the google servers verifies info (things like do the fingerprints match the device in question) then returns with encrypted response... from that knowledge it would seem to be simpler to just hook safetynet and modify the requests it sends to the google servers...
someone else that has time should look into this
there is an exposed module that can help gain information its called inspeckage
Anyone successful getting tethering on the may update and magisk 16.4? I don't even see that module in the magisk repository anymore. Anyone have any advice, other than modifying build.prio? (Which I tried doing, still can't get it to work!)
Hi I rooted my tab s7+ sm-t970 but when I use magisk it give me a SafetyNetApi error it never passes can someone help me fix this. Thank you
I have the same exact issue.
Maybe could be our root?
homogamez said:
Maybe could be our root?
Click to expand...
Click to collapse
I guess its possible. It's been a long time since I've rooted something. When I open the Magisk app it says install next to magisk and the same for app. I hit install and it goes through the processes but nothing happens. There's no other area to add modules or anything. Can we go start over and do it again without breaking something? I'm lost. lol
It also happens on One Ace and N10
Hopefully next version will fix it
I can use banking app but not netflix. I get the red warning at boot up so I figure I gotta be rooted. Maybe I'll try adding TWRP
EDIT:
Went to backup using TWRP and said my device isn't rooted. I give up. lol
There's a discussion about this issue. There's an error on API key.
You can get Safety net check from play store and see the actual results
Let me look for this thread because I don’t see a way to fix
Safetynet api error
Hello looking for help as I can't figure out what's wrong. I've tried downloading the code on only wifi and only mobile data and I still get the api error. I'm not running any add blockers. Using magisk canary.
forum.xda-developers.com
I'm about to become your favorite person ever, everyone! I am currently passing SafetyNet after flashing the kdrag0n safetynet-fix to my Samsung Galaxy Tab S7+ SM-T970 and enabling the MagiskHide Props Config module in Magisk.
HOWEVER, as was the case with literally all of the stock-based ROMs for the Galaxy S8, it appears that there will still be issues with a select few apps. For example, you will get soft-banned from Snapchat every few days. Also, certain healthcare apps will still be able to detect root (likely all related to Knox, since a Pixel 5 rooted via the same methods will launch the same apps without issue).
All the best from your fellow tinkerer - Godless1
(P.S. I'm going to copy and paste this into its own thread for better visibility.)
So, im new to rooting devices and stuff, but recently i tried to root my old samsung a50. At first it seemed like I succesfully rooted the phone, but then i found out magisk wasnt working correctly. I found out that zygisk was the problem, so i googled and tried some fixes. After a while I got stuck in a bootloop. The next day I got everything working again (including zygisk) by doing a full reset and trying again. Then, when I tried to add apps to the zygisk special list (or something like that i forgot what its called), i rebooted my phone because it said i would have to do that to make my changes work. After I did that everything has stopped working. Root checker doesnt even confirm that the phone is rooted at all and magisk, zygisk and ramdisk dont seem to be working either if i look at it in the magisk app.
Does anyone know if there is a way to fix this? Ive looked all over redit but couldnt find anything.
Btw i used these instructions:
https://forum.xda-developers.com/t/guide-root-unroot-rooting-unrooting-a505fn.4447651/#post-88239721
If screenshots are neccesairy let me know, but they will be in dutch so i figured it wouldnt really help.
Edit:
I kindoff fixed it. I went in to orangefox recovery and then rebooted trough that service selecting recovery. Now root checker does confirm the device is rooted and magisk seems to be working, but not completely. It still says that ramdisk is dissabled. Any advice on how to fix this? or does it even matter?
My A50 also says that Ramdisk is disabled and I haven't found a way to fix it, and since it's an A-only device it's really hard to flash Magisk. I hope you find a way to fix it