Any way to run pokemon go on rooted devices cm14.1, RR :fingers-crossed:
Past Solution
When i tried to use pokemon go on cyanogen mod 13, i had to download smanager (I'm new, so I couldn´t post the link, search it on google play), went to bin and xbin folder and changed the name of the root folder for .root in both folders and it worked, I don't know if this works now ´cause I'm not playing anymore
I hope this work
No... Pokemon Go uses the SafetyNet API, which on custom ROMs there is no way around (read up on the SafetyNet API and you will understand why pretty quick). On stock rooted there are some exploits but they seem to get patched almost as fast as they are put into place.
krisbeowolf said:
Any way to run pokemon go on rooted devices cm14.1, RR :fingers-crossed:
Click to expand...
Click to collapse
delete "su" file from system/bin and system/xbin, then reboot.
tested on RR. it works
but you'll lose root access after restart
Related
Newest update has blocked access to rooted phones. Even after hiding/ removing root access privileges (I've tried both hiding and un-rooting) I cannot log in, so I'm left only to assume that the version of the OS itself is blocked.
Simple question: Does anyone know of a way around this? I see hundreds of posts about magisk, but I cannot do that while using slimkat ( magisk requires android 5.0+)
I've really gotten into this game over the last coiuple months, but I refuse to revert to some vanilla stock version of android to play. If anyone could provide any info I'd greatly appreciate it.
I'd do what I always do when I need/want to run something of that nature: I install a "sacrificial ROM" alongside my Slim using MultiRom and boot into it when needed.
So...an app demands a non-rooted ROM? No problem: Here's a plain vanilla AOS sandbox for you to play in.
I'm playing to PoGo with any issues with SlimRom 6, I just deleted a file called su.bin from /system/bin and /system/xbin.
This erases root of the rom, and make it playable. Use SafetyNetHelper on Google Play Store to check if you pass the test (PoGo uses this test).
You can delete them (you have to delete both) on the file manager of TWRP.
The way i got mine to work(i can also use the Fake GPS hack with my POgo as well! ) is 1st i downloaded an already rooted(with SuperSU) rom for my phone off of xda and i installed the fake gps app through ucky patcher to make it a system app. i then downloaded a stock rom for my phone from here at xda, and i flashed it using Odin, this replaced everything to make it stock again but kept my system files(the fake gps app) so then all i had to do was redownload PoGo and login as normal and voila! their security check diverted and still able to fake gps it lol
Hi everybody I don't usually post and ask for help but this has got me stumped I have been trying for so long now to get root and Pokémon go to work side by side
This is what I can and have tried so far .
I install fresh cm13 if I delete the su files in xbin and bin then Pokemon works OK but I have lost my root . this is the only way I can get it too work at all
I have read posts on installing superSU and Hidesu with systemless xposed. After many days of trying I manages to get both installed and thought it would work but I still get the "this device is not compatible "
The steps I took were to do a full clean install of cm13 remove the su files reboot into recovery install xposed systemless 82 followed by SuperSU zip file and then hidesu all installed fine rebooted and got the incompatible message on pokemon I then uninstalled the systemless which also didn't work I tried the suhide GUI and I also tried the latest root switch .
I am sure there are many questions on this I have read so many posts on how to do this but for some reason it's not working for me .
If anybody could help me or maybe tell me where I am going wrong ? As I just don't want to lose root for Pokémon go
Many thanks in advance
**CONTINUE AT YOUR OWN RISK**
**I ASSUME YOU KNOW HOW TO SAFELY NAVIGATE /SYSTEM & ADJUST FILES AND THEIR PERMISSIONS**
This is a write up on how to install and use the stock Google Phone app.
Yes there are simpler ways to achieve something similar. There are a few developers on xda who have patched the Google Phone app so you don't have to do the following.
I personally enjoys the harder things in life. Along with just jumping on Apkmirror and installing any new updates to the phone app without waiting for someone to patch it.
Google Play Store won't allow you to find or update (as far as I know) the Google Phone app unless your phones identifies itself to the store as a pixel. If you did manage to get your hands on the apk it'll fail to install.
(I've seen a few magisk modules that will work)
However thanks to Apkmirror and the opengapps GitHub you could get around this.
First you need to get the files that the Google Phone app requires to be within the /system partition.
com.google.android.dialer.support.xml
com.google.android.dialer.support.jar (I use API 27)
The .xml goes in /system/etc/permissions with root permissions and the .jar goes in /system/Framework also with root permissions.
So either use your favorite root file manager, TWRP, adb, and place the files in their respective location and adjust the permissions. I personally either use TWRP or adb and adjust the permissions via the chmod 0644 command on the files.
Once you have verified the files are where they belong and have the correct permissions. Install the apk, set it as the default phone app and enjoy. (Adjust all permissions to your liking)
https://github.com/opengapps/all/tree/master/
View the code and find the files.
Thank you GitHub, Opengapps, and who ever uploads the files to Apkmirror.
Information I gathered over the years and random old xda threads. Also serves as a post I can reflect back on two months from now when I forget again.
ENJOY and don't do something if you don't understand, accept responsibility for your own actions because I won't for you. Go explore the wonders of learning Linux, and have plenty of backups to fix your non fatal mistakes.
It works great, thanks!
Tachi91 said:
**CONTINUE AT YOUR OWN RISK**
**I ASSUME YOU KNOW HOW TO SAFELY NAVIGATE /SYSTEM & ADJUST FILES AND THEIR PERMISSIONS**
This is a write up on how to install and use the stock Google Phone app.
Yes there are simpler ways to achieve something similar. There are a few developers on xda who have patched the Google Phone app so you don't have to do the following.
I personally enjoys the harder things in life. Along with just jumping on Apkmirror and installing any new updates to the phone app without waiting for someone to patch it.
Google Play Store won't allow you to find or update (as far as I know) the Google Phone app unless your phones identifies itself to the store as a pixel. If you did manage to get your hands on the apk it'll fail to install.
(I've seen a few magisk modules that will work)
However thanks to Apkmirror and the opengapps GitHub you could get around this.
First you need to get the files that the Google Phone app requires to be within the /system partition.
com.google.android.dialer.support.xml
com.google.android.dialer.support.jar (I use API 27)
The .xml goes in /system/etc/permissions with root permissions and the .jar goes in /system/Framework also with root permissions.
So either use your favorite root file manager, TWRP, adb, and place the files in their respective location and adjust the permissions. I personally either use TWRP or adb and adjust the permissions via the chmod 0644 command on the files.
Once you have verified the files are where they belong and have the correct permissions. Install the apk, set it as the default phone app and enjoy. (Adjust all permissions to your liking)
https://github.com/opengapps/all/tree/master/
View the code and find the files.
Thank you GitHub, Opengapps, and who ever uploads the files to Apkmirror.
Information I gathered over the years and random old xda threads. Also serves as a post I can reflect back on two months from now when I forget again.
ENJOY and don't do something if you don't understand, accept responsibility for your own actions because I won't for you. Go explore the wonders of learning Linux, and have plenty of backups to fix your non fatal mistakes.
Click to expand...
Click to collapse
You could use Magisk an PIX3LIFY module, it should do all that for you...
Anyway, does Google Phone work just fine without any crash? Because I have Android Oreo 8.0 on my HTC 10 and I've tried to get Google Phone working but it crashes when you give contacts permissions and access your call history or the dialer keypad. Do you not have these problems on your U12+ with Android Oreo 8.0?
rfgamaral said:
You could use Magisk an PIX3LIFY module, it should do all that for you...
Anyway, does Google Phone work just fine without any crash? Because I have Android Oreo 8.0 on my HTC 10 and I've tried to get Google Phone working but it crashes when you give contacts permissions and access your call history or the dialer keypad. Do you not have these problems on your U12+ with Android Oreo 8.0?
Click to expand...
Click to collapse
Works fine for me, no issues.
In the past ive seen it crash from either wrong file permissions or incorrect framework or xml file.
I changed phone and It works great on the Rog Phone too. No crashes at all.
Hi. Newbie here. Want to install the Google dialer on wife's HTC U12+ but the link is dead? Any assistance would be greatly appreciated. Happy wife happy life?
I think anyone who tried flashing Magisk on any of the latest phh GSI discovered that wifi, mobile data and calls suddenly get their teeth kicked in.
Since nobody appears to care about that issue much, we have to make do with a workaround.
Credits go to @xJovs for being the one to actually provide proper steps in this post, but since not many people will be lucky enough to stumble upon it while desperately searching through threads, I decided to make a thread here for all the lost souls.
Although the custom kernel part is supposedly optional, one can't say no to a functional custom kernel on Pie.
1. Download the ab superuser and the superuser apk from HERE and the SmurfKernel
2. Get your hands on a TWRP image
3. Boot into it with fastboot ( at the moment we can only boot into TWRP since Magisk is a no go )
4. Flash the SmurfKernel
5. Reboot into the OS
6. Boot into TWRP again
7. Flash the superuser ab zip
8. Boot into the OS and install the Superuser apk
9. Enjoy raw root permissions ( without all the Magisk goodies but still better than nothing )
Niiiiiiice
Also no one cares that substratum still won't work with this root method anyone found also a workaround for that ?
CroW_D said:
Also no one cares that substratum still won't work with this root method anyone found also a workaround for that ?
Click to expand...
Click to collapse
Yeah, I don't know why it won't work. Root permission should be root permission, after all.
The Marionette said:
Yeah, I don't know why it won't work. Root permission should be root permission, after all.
Click to expand...
Click to collapse
I thinks since it needs vendor 9.0 and not 8.1 could be
CroW_D said:
I thinks since it needs vendor 9.0 and not 8.1 could be
Click to expand...
Click to collapse
Vendor should have no effect on root permission.
And we can't use the 9.0 vendor on any phh GSI due to incompatibility.
The Marionette said:
Vendor should have no effect on root permission.
And we can't use the 9.0 vendor on any phh GSI due to incompatibility.
Click to expand...
Click to collapse
I tried with coming from h2os last time and magisk and subs was working but breaking other things. So I guess it should be vendor
This method kinda roots the phone. You can't use system root. Things like moving files through root explorer won't work cause you can't access system root. Things like substratum won't work cause of that
Nice Work and thanks for sharing!
romen288 said:
This method kinda roots the phone. You can't use system root. Things like moving files through root explorer won't work cause you can't access system root. Things like substratum won't work cause of that
Click to expand...
Click to collapse
I guessed that but didn't get to confirm it since I switched back to OOS Beta 1.
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.