Related
Hi.
I just read that you will no longer be able to play Pokemon Go if your phone is has root.
Can someone confirm this? If so.. They have just shot themselves in the foot.
"Ahead of the Pokemon Go Plus launching next week, Niantic (unsurprisingly) is now pushing out a new update to the app that brings support for the accessory, along with a few other goodies. Last week, they announced that a new Buddy system would be added in a future update, a feature you’ll be able to enjoy in this latest release (version 0.37.0). Here’s the full changelog:
Implemented Buddy Pokémon: Trainers will now be able to choose one of their Pokémon to be their buddy. A Trainer can earn Candy for their Buddy Pokémon by walking a certain distance.
Made it easier to select smaller Pokémon on the screen.
Fixed an issue where Eggs would sometimes hatch without displaying the animation.
Improved performance reliability when a device switches networks to no longer cause the application to hang or stop updating.
Pokémon GO Plus support
Minor text fixes.
The exact distance you’ll have to walk Pokemon to gain candies — and the exact amount received — still hasn’t been determined. It sounds like they’ve finally been patching a few annoying bugs and although it wasn’t mentioned in the changelog, we hope the annoying way sounds gets muted whenever you receive a notification has been fixed as well.
In an effort to crack down on the amount of bots, scrapers, and cheating their way through the game, Niantic is also making the controversial move to prevent rooted or jailbroken users from playing the game. It’s unfortunate for those with rooted devices playing the game legit, but since this is how GPS spoofers are cheating — and ruining the game for others — it was a logical move.
It could take awhile before you see the update hit the Play Store on your Android device, so don’t freak out if you don’t see it right away. We’re sure it’s just a matter of time before the APK appears and once it does, we’ll post here for you guys."
http://phandroid.com/2016/09/10/pokemon-go-0370-update-buddy-system-no-root/
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here is the fix.
Magisk
Everyting you need to know is in that thread. Search it.
Remeber to uninstall xposed if you have it.
This is the right xposed for Magisk.
Xposed v86.5
And the Material Design Xposed Installer
1. Unroot completely and i do mean completely
2. Flash Magisk
3. (Optional flash xposed)
4. Wipe Dalvik/Cache
5. When you reboot don't let the kernel reroot.
6. When booted flash the rest.
7. Use Magisk app to turn off root
8. Play Pokémon 0.37
//Tesla
Well, I wont update until it is in the playstore.. I guess I will find out then
EDIT: I am too curious so I tried to update the app and IT IS WORKING WITH MAGISK ROOT
CrazyCypher said:
Well, I wont update until it is in the playstore.. I guess I will find out then
EDIT: I am too curious so I tried to update the app and IT IS WORKING WITH MAGISK ROOT
Click to expand...
Click to collapse
Could you tell us, how are you doing
CrazyCypher said:
Well, I wont update until it is in the playstore.. I guess I will find out then
EDIT: I am too curious so I tried to update the app and IT IS WORKING WITH MAGISK ROOT
Click to expand...
Click to collapse
How and can i use it with my rom and kernel in my sig?
Only a matter of time until they figure a way to block Magisk too. They're just overreacting anyway. Ingress blocks GPS spoofing, why can't this game do it too? I've seen it firsthand, Ingress just says "idk where you are you're using FakeGPS, sorry"
How do I install Magisk anyway?
With Magisk if it works smoothly .. .. because it uses the verification that has Android Pay ..
PoGo is much more popular than Android Pay, but I don't imagine many rooters will give up their root to play a game.
Niantic, and by extension, Google, just upped the ante in the arms race. Things are going to get ugly.
wow i actually liked the game but i guess this gives me more time to look at nature
segv11 said:
PoGo is much more popular than Android Pay, but I don't imagine many rooters will give up their root to play a game.
Niantic, and by extension, Google, just upped the ante in the arms race. Things are going to get ugly.
Click to expand...
Click to collapse
Niantic made Ingress...and Ingress blocks GPS spoofing, even in the way that it works in Pokemon Go. Why can't they just fix that and not eff with rooted users?
---------- Post added at 04:47 PM ---------- Previous post was at 04:31 PM ----------
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Guide on how to install Magisk and stuff and use Pokemon Go.
segv11 said:
PoGo is much more popular than Android Pay, but I don't imagine many rooters will give up their root to play a game.
Niantic, and by extension, Google, just upped the ante in the arms race. Things are going to get ugly.
Click to expand...
Click to collapse
It's not that important to me.
Sent from my SM-N930P using XDA-Developers mobile app
Question... Can't I just uncheck root in SuperSU's settings and run it that way? (I have not gotten the new update yet so I'm asking beforehand). Magisk appears to have this option. Or do I need to totally uninstall SuperSU by dirty flashing the ROM again, and not SuperSU?
agentfazexx said:
Question... Can't I just uncheck root in SuperSU's settings and run it that way? (I have not gotten the new update yet so I'm asking beforehand). Magisk appears to have this option. Or do I need to totally uninstall SuperSU by dirty flashing the ROM again, and not SuperSU?
Click to expand...
Click to collapse
Simply unchecking root will not work. You have to use systemless root
SecSpyral said:
Simply unchecking root will not work. You have to use systemless root
Click to expand...
Click to collapse
Well, guess I'm not updating then.
The fix --- > http://forum.xda-developers.com/showpost.php?p=68625159&postcount=1
Tesla said:
The fix --- > http://forum.xda-developers.com/showpost.php?p=68625159&postcount=1
Click to expand...
Click to collapse
So by completely unroot...Can I accomplish this by going into TWRP, clearing cache/dalvik, flashing again the ROM, GApps, kernel and skipping SuperSU..then installing Magisk? I really don't want to have to do a clean install just for this.
Unless you want to do a clean install skip ROM, Gapps and kernel.
Do a unroot in SuperSU. Then look for root-files in system. Like the OP in Magisk says.
After that install Magisk in TWRP.
Tesla said:
Unless you want to do a clean install skip ROM, Gapps and kernel.
Do a unroot in SuperSU. Then look for root-files in system. Like the OP in Magisk says.
After that install Magisk in TWRP.
Click to expand...
Click to collapse
Oh so I don't need to reflash anything?
I'll check the Magisk thread and post there I guess if I get stuck.
agentfazexx said:
Oh so I don't need to reflash anything?
I'll check the Magisk thread and post there I guess if I get stuck.
Click to expand...
Click to collapse
I didn't
Worked for me.
Tesla said:
I didn't
Worked for me.
Click to expand...
Click to collapse
Even if I installed SuperSU via the zip? Just unroot in the app and I'm good?
agentfazexx said:
Even if I installed SuperSU via the zip? Just unroot in the app and I'm good?
Click to expand...
Click to collapse
It's phh's SuperUser you are to flash.
Do this and check back with me.
1. Uninstall root&superuserSU
2. Open TWRP
3. Flash magisk uninstall
4. Flash magisk v6
5. Flash phh's SuperUser
6. Reboot
7. Install ppsuperuser app
8. Install magisk app
This is a starter thread for getting Nintendo's latest Android app (which has finally come from iOS over three months later), Super Mario Run, to work on Android devices that have been rooted and possibly have no Google Play Store installed. Developers, please contribute your findings!
It worked with root but I got an error when I finished the tutorial. Then I saved my game with a Nintendo account and I cleared game data. I've used magisk hide with this game and I can play again
apfo said:
It worked with root but I got an error when I finished the tutorial. Then I saved my game with a Nintendo account and I cleared game data. I've used magisk hide with this game and I can play again
Click to expand...
Click to collapse
I used magisk too but I can't find where I can hide.. can you help me? Do I need to install a module?
n0m1s said:
I used magisk too but I can't find where I can hide.. can you help me? Do I need to install a module?
Click to expand...
Click to collapse
After you've installed Magisk you just need to go to the Settings in the Magisk Manager APP and enable Magiskhide and then you should See a new tab for Magisk hide in the Manager APP and just select the Apps you want to hide root.
(Sorry for my Bad English)
ApollosRage said:
After you've installed Magisk you just need to go to the Settings in the Magisk Manager APP and enable Magiskhide and then you should See a new tab for Magisk hide in the Manager APP and just select the Apps you want to hide root.
(Sorry for my Bad English)
Click to expand...
Click to collapse
Thanks for that, but it's not working too
ApollosRage said:
After you've installed Magisk you just need to go to the Settings in the Magisk Manager APP and enable Magiskhide and then you should See a new tab for Magisk hide in the Manager APP and just select the Apps you want to hide root.
(Sorry for my Bad English)
Click to expand...
Click to collapse
I did exactly what you did and it worked fine for me.
So do I flash via twrp the zip in the magisk post?
I use magisk to hide mario but when i pass the tutorial send error 804 5100 and have to delete the Account:.xml located in /data/data/com.nintendo.zara/sharedfolder and then log in with my account so brings my save but i complete 1 course and the same error again and have to do it all over again, does anybody find a solution for this?
Is magisk a supersu replacement or can I just install alongside? It also says it requires 5.x so no 4.4?
Magisk work great for me
simbin said:
Is magisk a supersu replacement or can I just install alongside? It also says it requires 5.x so no 4.4?
Click to expand...
Click to collapse
it is a supersu replacement but the magisk is great and has better functions and the moduls are great, forget the turning off part and the the recovery and flash the zip, the magisk do it all for you!
Mago6246 said:
it is a supersu replacement but the magisk is great and has better functions and the moduls are great, forget the turning off part and the the recovery and flash the zip, the magisk do it all for you!
Click to expand...
Click to collapse
Don't think magisk works with cm12 on Amzn Fire Phone bc bootloader isn't actually unlocked. They should limit SafetyNet to Leaderboards - pretty sure that's what all the fuss is about. Fine, Nintendont take my money!
Magisk Manager won't install Magisk on my rooted S7 Edge. I've read that it's not compatible with Samsung devices right now, don't know if that's true. How else can I make Super Mario Run work?
suhide give me bootloop with lineos so I will try magisk
simbin said:
Is magisk a supersu replacement or can I just install alongside? It also says it requires 5.x so no 4.4?
Click to expand...
Click to collapse
Yes, You can use it alongside with SuperSU.
Hi !
Same error for me... I installed Magisk, uninstalled SuperSU, set the Super Mario App to hide but i still get the error...
Did I miss something ?
Thanks
Rooted Nexus 5 running Cataclysm 6.0.1
Miitomo was patched using a special security bypasser made for it, and also with XPosed and RootCloak. Is there a similar method for those who seem to have issues using Magisk?
I myself haven't tried Magisk. I'll see how it works on my Galaxy S7. :fingers-crossed:
Xda, please merge this thread with the other thread that I made. I accidentally made a duplicate.
I do not have Google Play services installed, and it seems to need it.
I'm currently running Magisk with Magisk Hide on and RootCloak as well and it keeps erroring out. Currently the only workaround I've found is deleting the deviceAccount xml file in the app prefs folder. I have a feeling it has something to do with xposed or safetynet that's causing it to fail. I enjoy the game enough that I wouldn't mind buying it, but not if Nintendo is going to lock users out like this.
Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.
SuperSU is not working in the Pixel with 8.1
Sh0X31 said:
SuperSU is not working in the Pixel with 8.1
Click to expand...
Click to collapse
Oh. I had no idea.
Do any root methods that aren't Magisk work?
daddylonglegs said:
Oh. I had no idea.
Do any root methods that aren't Magisk work?
Click to expand...
Click to collapse
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me
daddylonglegs said:
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me
Click to expand...
Click to collapse
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.
Click to expand...
Click to collapse
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.
daddylonglegs said:
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.
Click to expand...
Click to collapse
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough
Click to expand...
Click to collapse
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?
daddylonglegs said:
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?
Click to expand...
Click to collapse
I don't flash twrp zip, just boot it, I know twrp on pixel oreo has still some troubles.
You can try to put your pin and AFTER (when you are on the main scrren with all the actions) plug the otg. On nougat this worked for me, now I just put the 2 or 3 files in internal storage so I don't use otg anymore from recovery so I don't know if this method works or not.
daddylonglegs said:
Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.
Click to expand...
Click to collapse
Install ElementalX before TWRP if you wish to install TWRP.
SuperSU is no longer maintained and will not work any longer on modern versions of Android until further notice.
About the "internal problem" this can be completely ignored and does not harm the functionality of the device whatsoever.
Magisk 16.3 is the best version of Magisk and mounting USB-OTG shouldn't be problematic whatsoever. Mounting the drive in TWRP has no effect on it mounting in the system and vice-versa.
To mount the OTG in TWRP, plug it in, go to "mount" and select storage location, here you can choose between the internal sdcard and the USB-OTG storage device.
Regarding the mounting of the USB-OTG device in Android the drive must be formatted using a filesystem/partition scheme that Android is capable of mounting. I think FAT32 is the most compatible option.
Applications won't just magically see the external storage unless they're made to support such devices. Google kinda messed up some external storage functionality in Nougat and Oreo, it's kind of quirky. :silly:
Does anyone have experience with turning a user app into a system app on 9.0?
I tried using terminal emulator + app systemizer on magisk and Link2DS both ways have corrupted the phone.
kittygotwet said:
Does anyone have experience with turning a user app into a system app on 9.0?
I tried using terminal emulator + app systemizer on magisk and Link2DS both ways have corrupted the phone.
Click to expand...
Click to collapse
Are you able to recover? If so, you may have to settle without it. I know Systemizer works on 8.1, but I didn't try it on 9.0 before I downgraded. I'm not aware of any other options besides manually moving it, but that would break your systemless root, and would also need to be done after every update.
If you can't recover but can get into fastboot, you can boot into TWRP and flash "Magisk Mount". That will allow you to remove the Systemizer module manually from the Magisk image and boot back into the OS. As for Link2SD, I've never used it, so I'm not sure what changes it made that would have to be undone in order to recover.
jallenhayslett said:
Are you able to recover? If so, you may have to settle without it. I know Systemizer works on 8.1, but I didn't try it on 9.0 before I downgraded. I'm not aware of any other options besides manually moving it, but that would break your systemless root, and would also need to be done after every update.
If you can't recover but can get into fastboot, you can boot into TWRP and flash "Magisk Mount". That will allow you to remove the Systemizer module manually from the Magisk image and boot back into the OS. As for Link2SD, I've never used it, so I'm not sure what changes it made that would have to be undone in order to recover.
Click to expand...
Click to collapse
I just flash-all to fix it then reroot with Magisk. How do I convert an app to system through recovery (in twrp)?
kittygotwet said:
I just flash-all to fix it then reroot with Magisk. How do I convert an app to system through recovery (in twrp)?
Click to expand...
Click to collapse
As long as you dont care about remaining systemless and passing SafetyNet, you could simply move the apk folder into the system app folder manually. You could do it either through TWRP's built in file manager, or do it live with a root capable file manager. Either way should work.
Again, it's not ideal as it will trip SafetyNet and must be done after every ROM update/flash. So, if you have anything that depends on SafetyNet, that's not an option for you.
Another possibility would be to look at the Magisk documentation for module building and make your own module which would inject whatever apk you need systemlessly. You could accelerate the learning process by downloading one that already does something similar and reverse engineering it to fit your needs.
jallenhayslett said:
As long as you dont care about remaining systemless and passing SafetyNet, you could simply move the apk folder into the system app folder manually. You could do it either through TWRP's built in file manager, or do it live with a root capable file manager. Either way should work.
Again, it's not ideal as it will trip SafetyNet and must be done after every ROM update/flash. So, if you have anything that depends on SafetyNet, that's not an option for you.
Another possibility would be to look at the Magisk documentation for module building and make your own module which would inject whatever apk you need systemlessly. You could accelerate the learning process by downloading one that already does something similar and reverse engineering it to fit your needs.
Click to expand...
Click to collapse
damn, i need safetynet for google pay. crap hopefully the apps update for 9.0 and fixes itself.
My daughter got a new phone, after struggling with bootloops and magisk issues. Finally got everything working correctly.
But,
I got root to go fine, only thing is she has had location issues. Google maps, other GPS or location services did not work.
So I uninstalled xprivacylua and seems like services came back, looks like I wasn't hiding anything on it anyways. Or I don't remember what it was.
So instead of reinstalling xprivacylua I decided to look for different answers .
Maybe some other solutions.
Here is a list of apps and modules that are installed. I think some of them overlapped and are kind of messed up. To many that my head is spinning.
Magisk
23.0 (23000)
Magiskhide Props Config.
Riru
Riru LS exposed (Tried switching back and forth to edxposed)
Systemless Hosts
Universal Safetynet fix 1.1.2. (Tried different versions)
LS Esposed one module,
Hiddencore module (enabled Google services Framework and google play services)
Also cleared Data and Cache on google play store.
Rebooted every time
Always safety net failure.
I know its a lot to take in , and do appreciate any feedback or help on this issue.
Is it an 8T? Are you running stock OOS with magisk?
In that case all you need to pass safteynet should be Magisk 23 with magisk hide activated. No need to bother with Magisk hide propconfig, or edexposed or anything.
If you are running a custom rom it is a different matter
I have magisk 23 and magisk hide is active on all google play services, but it still fails.
Its 8t with stock rom.
I think this is why its a little confusing since on my stock 7 pro I have google play services and only android.gms, and android gms unstable hidden and it works fine.
There is not a custom recovery on either of these phones.
Magisk and magisk hide works fine for me, so don't know what to say.
Perhaps try to uninstall Riru and exposed to make sure that they aren't triggering safety net?
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Screens of magisk hide props config
scottlam1 said:
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Click to expand...
Click to collapse
Nope.. Terminal Emulator is actually recommended. With Termux, you are required to use root access for props to work.
with Terminal Emulator, you can just type:
props
and then it'll load. no "su" necessary. That's termux. I've had some issues that these people are talking about with my OnePlus 8T (KB2005, unlocked completely).. I'll try Termux just to rule this out, but this is highly doubtful as to whether or not safetynet passes based on this--it's attempting to modify the same values. Anyway, when I unlocked that bootloader on a stock rom, CTS Profile started showing as false. So I did get the stock on there correctly and it initially passed with a LOCKED bootloader. There's an alpha TWRP that you can actually flash if you want. There's a couple others where you can only boot it.. there's a lot of "only's" here.. and I couldn't get it going with any of the apps mentioned, including ditching EdXposed and deciding to try LSPosed, but that + XPrivacyLau didnt seem to help me. Maybe I'm doing something wrong. From what I can tell I've done everything right and I've got quite a bit of experience attempting/doing this. Sometimes Device SImulation and forced BASIC ATTESTATION can be a lifesaver.
On my OnePlus 6T, I don't have this problem.. then again it's on Android 10. I can't even get a proper root explorer for Android 11. I seriously can't stand what they did to Android 11.. it's so ridiculous how many apps are now incompatible. Root Explorer Pro was possibly the best Root File Manager I've ever used and I've used it since day 1.
Anyway, I'm gonna give all of this a shot in different order.. and this time I'll see if Magisk can do the trick (last time it was on some different firmware and i just now was able to get it going by flashing via Fastboot in Linux). It's the manual way (payload dumper) as opposed to MSMDownloadTool -- which could be used via a VM.. and maybe even better than using Windows tools where you literally have no idea what you're actually doing. I'm just saying. Android is a linux distro, technically.. and we're trying to use just basic root apps for Android 11, and they don't seem to work.. it's insane. They did something with the partitions and it's apparently having issues even mounting R/W even with Magisk giving it root permissions. Btw, Magisk Canary is now outdated, as far as I can tell? Or it's just nowhere to be found when it comes to versions. Either way, I have tried multiple. So I'll try again in a different order.
Sorry for the long post. I've just had it. I've been working on this for a WEEK non stop.. 5-6 days and this is the first sign of progress (reverting via fastboot via Linux, which is the same thing as the MSMDownloadTool ultimately... without the hassle of finding it)
Let me know if there's anything else.. cause I've tried just about everything out there. Remember, for me, so far... unlocked bootloader = CTS Profile failure.. but locked bootloader + stock rom? Passed. I don't know. Before it wasn't passing with a stock rom that came with it so that drove me nuts and made no sense, hence me saying "progress" ... heh. Anyway.. Please let me know if you guys do find anything that works for it. I'm at my wits end. There's basically almost zero support for the 8T but plenty for the 8 and 8 Pro. So that also gets on my nerves. Sorry, once again, for this really long post. Some of it is just venting and I'll update if I get somewhere with it.
.. and now this morning after installing magisk, by just booting twrp (not flashing, but booting) and then using LSPosed/XPrivacyLua (I installed MagiskProps too but I barely did anything aside from pick a fingerprint) --- and it passed? WHAT?
I'm gonna look into this, but I'm not complaining. Let's see if I can find good Android 11 apps for actually browsing the system and being able to r/w any elusive partitions -- wasn't working well with Android 11 before. Not sure if that's around with a simple design anymore. Root Explorer Pro was king of that. Then Android 11 stepped in. I still have to install Lucky Patcher, if it will even work as a module for LSPosed. (Yes, I'm one of those idiots) -- I fully expect it to fail with that but I might be pleasantly surprised. Who knows. So, we'll just call this mixed results. For now -- Passing somehow. I don't understand aside from LSPosed and XPrivLua.. maybe magiskprops. Not sure which one did what first to cause this to go the right direction.
All I can say is all I have is magisk props not the other 2 modules you speak of
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
eracet said:
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
Click to expand...
Click to collapse
Ok asked her what she did. Mentioned updated YouTube vanced. And not sure of anything else.