Failed to detect location. (12) even with Smali Patcher + GPS Joystick Ninja
My phone is LG V20 using a rooted stock Oreo rom.
I've correctly followed the instructions for Smali patcher.
I've turned off all the settings in Ninja's GPS Joystick app
I've enabled mock settings on Developer Options
I've hid Magisk Manager
I've set the Location to Device Only
I've paused the Location History for Google
I've turned off "Find My Device"
I've enabled Magisk Hide on Google Play Services, Pokemon GO, and GPS app.
I've turned on privacy mode and generated a new app under a different name
I've even removed PKGO, Smali, and GPS app and reinstalled everything
Please tell me what to do. I've done literally everything there is to think of trying to get rid of the "Failed to detect location (12)" error. I spent hours trying to figure this out and it's stressing me the hell out.
I have. Core mode is off too. The module should be fully functional. I'm thinking it might be an issue regarding the Oreo stock rom I downloaded here
Ah shoot. I would but I just gave in and flash Lineage 16. Everything works again. Thanks for the quick reply!Post your magisk log.. we can try verify if the module is being loaded.
ANY POCO F1 USER PLZ HELP?
I am unable to make patch because my pc is not working.
Can anyone upload Smali patcher for miui
10.3.4.0 ?
Thanks
fOmey @ XDA
Patcher Version: 0.0.4.9
==> Detected Java: 1.8.0_211
==> Dumped framework
[INFO] Processing 1 file(s) from bin\services.vdex
[INFO] 1 out of 1 Vdex files have been processed
==> Extracted classes.dex
I: Using Apktool 2.4.0 on services.jar
I: Baksmaling classes.dex...
I: Copying assets and libs...
I: Copying unknown files...
I: Copying original files...
==> Patched mock location boolean
==> Patched mock location boolean
==> Patched secure flag function
==> Patched secure capture function
==> Patched secure capture function
I: Using Apktool 2.4.0
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Building apk file...
I: Copying unknown files/dir...
I: Built apk...
W: Could not find resources
Processing 1 file(s) from bin\services.vdex
Processing 1 file(s) from bin\services.vdex
You are patching odexed file services.vdex
You need to deodex services.vdex first and receive services.jar.
https://xdaforums.com/showpost.php?p=79399590&postcount=2812
The problem is related to the magisk template download, not the patching process.
(I don't use the signature spoofing either way)
Processing 1 file(s) from bin\services.vdex
You are patching odexed file services.vdex
You need to deodex services.vdex first and receive services.jar.
https://xdaforums.com/showpost.php?p=79399590&postcount=2812
Found the issue.
codeload.github.com was blocked by one of adblock blacklists.
@fOmey maybe smali patcher should handle a connectivity error case rather than just getting stuck?
Why the deodexation process is not indicated in the log when the program is working?The patcher automatically deodex's if its necessary during ADB method.. that's precisely what its doing in the log.
Why the deodexation process is not indicated in the log when the program is working?
Output of this information to the log was not provided?
fOmey @ XDA
Patcher Version: 0.0.4.9
==> Detected Java: 1.8.0_211
==> Dumped framework
[B][INFO] Processing 1 file(s) from bin\services.vdex
[INFO] 1 out of 1 Vdex files have been processed
==> Extracted classes.dex[/B]
I: Using Apktool 2.4.0 on services.jar
I: Baksmaling classes.dex...
I: Copying assets and libs...
I: Copying unknown files...
I: Copying original files...
==> Patched mock location boolean
==> Patched mock location boolean
==> Patched secure flag function
==> Patched secure capture function
==> Patched secure capture function
I: Using Apktool 2.4.0
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Building apk file...
I: Copying unknown files/dir...
I: Built apk...
W: Could not find resources
cuando termina de descargar binarys con el movil conectado le doy en adb patch y sale ERROR: no ADB devices found. ayuda no la e podido crear
Adb method works flawlessly on android 8.1 for Sony AOSP roms on X and XZ premium. The trick is to run the program in recovery (with system mounted obviously), to avoid permission issues.
Awesome tool!