Has anyone gotten latest version of PoGo working on latest Oreo with ElementalX? I've never played but my friends keep asking me to join so I figured what the heck..
Slight problem... Device Not Compatible??
I had magisk and xposed, but I tried disabling, and even fully uninstalling xposed (and all additional xposed modules), and adding PoGo to the MagiskHide options, with no luck.
It still says that my device is not compatible...I would assume that's due to the rooting?
Or is it because I'm using ElementalX kernel?
I read somewhere that there's a (not pokemon go-specific) bypass sort of thing involving SatefyNet, but you have to install Magisk *before* going through initial phone setup, but any guide I've ever read about flashing/rooting ph-1 says to go through setup and then install magisk. I tried to find the post that talks about it but I can't find it right now. Anyway, I would imagine there's some kind of checksum against system and if magisk has been added after the fact, the checksum wont match? I really have no idea, just a guess.
I haven't seen any other posts specifically mentioning Essential being incompatible, so maybe it's just me.
I was originally thinking it was because of root or magisk remnants(?), but maybe it's the non-stock kernel.
If anyone could help, I'd really appreciate it.
I feel silly asking such a noob question, I've just never play PoGo...or any Pokemon...ever.
extra info:
I have successfully created an account using their google auth option.
I get through the first Professor Willow part, then character selection.
Usually part way through character selection, I get the error in the attached image.
Its not on any one specific section, however, it can/has occur at any point during the loading.
I've cleared cache and data a hundred times because it seems to get further each time if I do a fresh data wipe and start over -- I know the next step already so I can get through faster maybe lol
--update--
I finally got through character selection and made it to the first chance to catch pokemon. I hit a squirtle and it was trying to break free, and then that error popped up.
Haven't been able to get back in far enough again to see if it actually added to my PokeDex or not.
Sorry for the late reply, but you have to hide root detection under magisk.
For Pokemon go to work, go to Magisk > MagiskHide > then search for Pokemon go and select it then reboot.
Related
Hi all,
After several annoying months of OTA boot loops, manual installations, and having to re-root my Marshmallow player, last month I finally installed Flashfire so I can do the monthly OTAs and stay rooted. I also switched back to stock recovery, if that helps to know. The bot on its side this morning was my first clue the patch had come out, so I rebooted the player and fired up Flashfire, which immediately sensed the update and asked if I would like to generate the actions to install it. I'm thrilled this is proceeding perfectly according to plan until I select OK and Flashfire crashes. Every time.
Chainfire would like to see the crash log if a post is needed in the Flashfire thread. Where might I find that? Every "logs" folder I've come across is empty. I have full-data logging enabled in SuperSU, but I'm also unsure where that file would be stored. Clearly I'm log-challenged.
I wouldn't mind staying that way if someone reading this might know what the trouble is to begin with. Thanks a bunch!
According to the Flashfire thread:
The log file can be found at /sdcard/FlashFire/lastlog on your device.
Click to expand...
Click to collapse
This location simply does not exist in my Nexus Player. Maybe I should have specified that in my original post, but I will now for anyone else who has the same problem and thinks they're going blind. Since no one in this particular forum seems to know where any other system activity logs are stored, I went on to the next suggestion, which is to use the Syslog app. Of course this has to be sideloaded, since the PlayStore thinks it isn't compatible with the Player. If the lack of easy navigation with a remote control is the reason for that verdict, they'd be right; yet I've managed to collect some data that I'm going to post over there in the hope it can be figured out why Flashfire becomes Crashfire upon attempting to do the OTA.
If anyone wants to know how it goes, you can find my post here. Wish me luck! :fingers-crossed:
Hello there. I have a question regarding getting my phone to be Google Play Protect certified again. I have unlocked the bootloader, which if I understand correctly is what breaks the certification, Flashed TWRP 3.0.4-1, and installed Magisk v20.4 via TWRP. I verified Root by using the app Root Checker on the play store (and also SU requests popped up after rebooting). I enabled MagiskHide inside Magisk Manager and performed a SafeyNet Check and both the ctsProfile and basicIntegrity returned as True (the first time I ran it cts failed so I enabled hide and rebooted). There are a few apps that I use that indicate my device is not compatible and it is because of this I am guessing (Chewy, Disney+ for example). Oddly, as I was typing this I tried again and looked in the "My Apps" list and I could install Disney+ from there (10 minutes ago I couldn't) but clicking on the app it still said that it was incompatible. Chewy, however, remains unable to be used.
Since I could only find references to this on this thread (https://forum.xda-developers.com/pixel-2-xl/help/play-certification-unlocked-bootloader-t3950857) and the second way to correct this problem, that thread says it doesn't resolve the ctsProfile) I figured I'd ask on here. I already soft-bricked it once and successfully used the MSM tool to bring it back so if I screwed something up I'll try again, but probably only once more :fingers-crossed:
*edit* I haven't activated my actual phone use yet since I want it to be stable first! Not sure if that makes a difference, I don't think it should.
*edit 2* I've since activated my phone. I can receive calls but no text messages. The plot thickens.
Thanks!
I recently moved to OOS11 and had trouble rooting. Now that I have my phone rooted I can no longer restart it or it will bootloop. Does anyone have any idea why that would be?
This will be the 3rd time I have MSMed my phone in the last 3 days.
As many problems as I'm having I'm thinking of just going back to Android 10.
Thanks in advance.
night hawk said:
I recently moved to OOS11 and had trouble rooting. Now that I have my phone rooted I can no longer restart it or it will bootloop. Does anyone have any idea why that would be?
This will be the 3rd time I have MSMed my phone in the last 3 days.
As many problems as I'm having I'm thinking of just going back to Android 10.
Thanks in advance.
Click to expand...
Click to collapse
Can you provide a bit more background, do you have any Magisk modules installed, does your phone boot at all? Did you patch your own boot.img just so that we can help you out better
Shredz98 said:
Can you provide a bit more background, do you have any Magisk modules installed, does your phone boot at all? Did you patch your own boot.img just so that we can help you out better
Click to expand...
Click to collapse
I'm patching my own boot.img and I only have skyvalex call recorder installed as a module. When it happens I just get stuck in an infinite boot animation with the two dots circling continuously.
I think I may have narrowed down the problem by going through the steps that I normally go through after MSMing my phone (I've done it 4 times now lol) and rebooting after each step to see what triggers it. Here are the steps in order.
1. MSM the phone and do bare minimum to get to home screen so I can enable OEM ulocking and usb debugging. (rebooted just fine)
2. Unlock bootloader with adb. (rebooted just fine)
3. Install magisk manager, switch to beta update channel, patch boot.img, flash patched boot.img (rebooted just fine)
4. Setup up phone with google account, set up fingerprint, etc (rebooted just fine)
5. Enable magisk hide and systemless hosts (rebooted just fine)
6. Restore a backup using oneplus switch from before this all started happening. (rebooted just fine)
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. I'm wondering if the new "use magisk module" mode in the newest version is causing the problem. Maybe if I installed EdXposed and used that like I used to maybe it would remedy the problem. Or maybe I should just use an adblock magisk module. However its far passed my bedtime so I will confirm this tomorrow if possible.
Disable the modules you have installed.
Reboot, does it loop?
If no then it's a module
If it does then it's your boot img
I'd recommend booting your patched boot img then directly installing via magisk (do not reboot until you have)
Hope this helps
night hawk said:
I'm patching my own boot.img and I only have skyvalex call recorder installed as a module. When it happens I just get stuck in an infinite boot animation with the two dots circling continuously.
I think I may have narrowed down the problem by going through the steps that I normally go through after MSMing my phone (I've done it 4 times now lol) and rebooting after each step to see what triggers it. Here are the steps in order.
1. MSM the phone and do bare minimum to get to home screen so I can enable OEM ulocking and usb debugging. (rebooted just fine)
2. Unlock bootloader with adb. (rebooted just fine)
3. Install magisk manager, switch to beta update channel, patch boot.img, flash patched boot.img (rebooted just fine)
4. Setup up phone with google account, set up fingerprint, etc (rebooted just fine)
5. Enable magisk hide and systemless hosts (rebooted just fine)
6. Restore a backup using oneplus switch from before this all started happening. (rebooted just fine)
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. I'm wondering if the new "use magisk module" mode in the newest version is causing the problem. Maybe if I installed EdXposed and used that like I used to maybe it would remedy the problem. Or maybe I should just use an adblock magisk module. However its far passed my bedtime so I will confirm this tomorrow if possible.
Click to expand...
Click to collapse
The issue is definitely lucky patcher, I had the same problem and my phone was useless until I got rid of it. So it seems it's not playing well with A11 or OOS11 in any case do not use it or you'll end up in a boot loop.
Cheers!
Ah lucky patcher..oh dear, can't help you with that crap.
Best advice, get rid
Bummer about Lucky Patcher....
In b4 the lock.
I can confirm the same findings, lucky patcher seems to break reboots later.
Hopefully a new version will find and resolve the issue, but until then not much we can do but to wait.
Unfortunately doesn't appear to be any way to get around this or recover from the bootloops without a wipe/reimage. Can't get access for adb during bootanimation, cant boot from a boot img, just basically stuck.
@OP, perhaps you can put a message in your thread's title just warning against LP on A11 for the time being.
uaktags said:
Unfortunately doesn't appear to be any way to get around this or recover from the bootloops without a wipe/reimage. Can't get access for adb during bootanimation, cant boot from a boot img, just basically stuck.
@OP, perhaps you can put a message in your thread's title just warning against LP on A11 for the time being.
Click to expand...
Click to collapse
I changed the title. Do we know if LP can be used with xposed on Android 11 with success still?
night hawk said:
I changed the title. Do we know if LP can be used with xposed on Android 11 with success still?
Click to expand...
Click to collapse
Did xposed work on 11?
night hawk said:
...
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. ...
Click to expand...
Click to collapse
@night hawk
Hi!
You better read the XDA Forum Rules and refrain from such topics. We don't accept discussions about issues with warez!
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Click to expand...
Click to collapse
THREAD CLOSED!
Im hoping someone can help me or possibly direct me to a youtube video to achieve what im looking to achieve
I struggled with, but finally managed to upgrade my device to stock 7.0, but rooted with magisk. When i tried to install xposed it forced a bootloop, so i restored a backup i had just made prior, and all has been well. I had wanted to install and use "Root cloak" as, at least so far thats been working on my 8.0 device (also Samsung, also stock but rooted but with SU method in that case, i couldnt get SU alone to work on my 7.0, for whatever reason)
I left it alone, but I'm noticing more and more that apps Id like to use come up saying "device is incompatible", which at first i thought it was weird as the play store itself allowed the install... but then upon some basic looking around, it seems that the apps have a way of detecting root, even through "magisk hide" - the feature directly included in magisk manager.
currently when i try to test for safetynet directly in the magisk manager, it doesnt actually properly test at all, no pass or fail, it just said unable
the rather peculiar part is that some of these apps arent all even banking apps, theyre for games. I cant figure out why gaming apps have issues with root access, especially when these apps themselves dont have root access, but thats kind of an aside
Any simplified help anyone can offer would be great! i am slightly familiar with editing the build prop, but i wouldnt know which values to change or even if that method is still effective. i used to use that on a quite older device (captivate glide) to spoof which version of android i was on in order to download app updates (which did work just fine, so why my older version wasnt supported is beyond me, lol)
thank you in advance for any help you can offer!
I was bored one evening, so I started poking around on XDA Forums, and found a way to fix the battery issue I had with OnePlus 3T that made me switch to another device years ago! I was surprised how usable 3T is to this day. I thought I would breathe some life into it with LineageOS 18.1 that continues to receive security updates and patches. This way I will have a backup phone ready in case something happens to my OnePlus 6. It is unlikely that 3T will receive LOS 19, so this guide should stay relevant for a long time.
1) Get back to the latest version of Oxygen OS if you are on a custom ROM. Use something like MSM Download tool and then upgrade to 9.0.6 with the built-in updater.
2) Follow the instructions on los website to install LineageOS 18.1 and google apps via MindTheGapps. If you do not need google apps, then you probably do not care about SafetyNet and do not need this guide
Now the main issue is the SafetyNet. If you install YASNAC - Yet Another SafetyNet Attestation Checker you will see that the phone is not passing the SafetyNet verification, meaning that Google Pay will not work and some other apps, like banking apps, might not work either. We are going to fix that with Magisk and MagiskHideProps. Feel free to poke around on your own. I will just present that have worked for me.
3) Go to Magisk's Github, download the latest release and follow the installation instructions. (Notes: 3T has RAM Disk, there is no separate vbmeta, boot.img is inside lineage-18.1-xxxx.zip)
4) Once you have Magisk working, got to MagiskHidePropsConf and get the latest release there. Go to Force Basic Attestation Post and follow the installation instructions under the spoiler.
5) Now, let's get Basic Integrity to pass. Go to Basic Attestation Post and make sure to add both com.google.android.gms.unstable and com.google.android.gms to deny list. Reboot. Go to YASNAC. It should say that Basic Integrity is passing. CTS profile match is not, but that's okay.
6) Install terminal app like Termux. Open it, and run su to get superuser privilages. Then run props. Follow the instructions to Edit device fingerprint (option 1).
Edit Device Fingerprint (1)
Pick a certified fingerprint (f)
Pick vendor (OnePlus is 21 at the time of writing)
Pick device (3T is 5 at the time of writing)
Pick the one with Android 9. (It does not matter that the android versions are mismatched)
Follow the instructions to apply changes and reboot.
7) Check YASNAC, everything should be passing now!
Some other suggestions:
GCam is pretty nice alternative to the original camera. I would recommend this one. (It is recommended to also install Google Photos. It is a google camera after all.)
OpenWeather is a nice weather provider.
I would also recommend going to Google's Keyboard, Messages, Phone, and Calendar Apps. AOSP ones are not great, in my opinion.
Hope somebody finds it useful! Good luck!
Ah nicely done, thanks for the effort and work you put into this. How is your 3T performing?
AndyC76 said:
Ah nicely done, thanks for the effort and work you put into this. How is your 3T?
Click to expand...
Click to collapse
Hi, thanks! I was planning to use it as a development device to pick up android app development, but life got in the way and that never got off the ground
My 3T has developed a battery issue which ultimately led to me retiring it. The battery is extremely unreliable. It can be at 1% but work for 3 hours, sometimes the phone refuses to charge and the battery percentage tends to get stuck at 50% regardless of the actual charge level. I tried replacing the battery but the same behavior persisted. I think it is something either with the motherboard or the battery connector on it :/ Still a pretty snappy phone though!