yashsingh1/xdaforums huggingface dataset:
[Magisk] Texas_Ace:
Yes, first ran setup, then installed the main nanomod file, then the fdroid, microG and patchers.

I tried it without the main nanomod file with the same results.

It takes ~8 mins or so to patch the phone so it is doing something and it completes successfully according to the script. Yet microG says that spoofing doesn't work.

I also tried installing it without magisk in system mode but got the same results (IIRC none of the nanomod items worked properly when I tried it in system mode, nothing was installed once booted even though it said it completed successfully ect but I tried so many things they all kind of run together now).
[Magisk] Setialpha:
Why did you flash FDroid and microG? It's already included in main mod. I guess they conflict.
[Magisk] Texas_Ace:
I tried just the main nanomod file early on and microg was missing so I assumed that it was not included in the main file and thats why there was a separate file for it. So I just started installing both after that.

They never seemed to conflict though, microg always worked fine if it showed up at all. It would just complain that signature spoofing was not enabled.

So the main nanomod file includes everything except the sig patcher?

The signature spoofer would not work no matter what I installed or what order I did it in (I reinstalled the phone at least a half dozen times testing this already).
[Magisk] bass@89:
Hi,

As suggested by
[MENTION=4187311]Setialpha[/MENTION] & [MENTION=7408621]noc.jfcbs[/MENTION]

Please follow installation steps exactly as described in screenshot.

FYKI,

Follow the setup procedure

1.NanoMod-setupwizard-14.4.20171014.zip (if you are selecting other than /data location)

Here you select what application you required select those. Like pseudo-debloating, other

apps,etc

2. Wipe everthing except Internal Storage & External Storage

3. Flash your ROM

4. Flash magisk (if you need & for pseudo-debloating)

5. Flash only NanoMod-14.4.20171014.zip

(don't flash everthing i.e microG,F-Droid. Because it is already included in NanoMod)

One more thing you for signature spoof don't flash NanoMod-patcher during ROM flash.

After following step.6 again reboot into recovery then flash Nano-Mod patcher for signature spoof.

6. After booting into ROM setup the microG

microG Setup

Once your ROM supports signature spoofing, you need to setup microG like this

go into microG settings and set up everything like:

check results in Self-Check, grant missing permissions (by tapping on them)

especially the Battery Optimization item

enable Google device registration

enable Google Cloud Messaging (only if you want to receive push messages from your applications)

enable Google SafetyNet (required for applications that utilize SafetyNet, for example Pokémon GO, ...)

'...' menu > set to use the Official Server

in UnifiedNlp Settings choose

Mozilla Location Backend as Geolocation backend

Nominatim as Address lockup backend

after everything is done, reboot

7. Boot into recovery, flash NanoMod-patcher-14.4.20171014.zip then reboot

After this step your signature spoof will work like charm.

go to Play Store, setup account and install your apps
[Magisk] Texas_Ace:
Ah, so you need to flash the spoofer after setting up microG, I think I tried this but not 100% sure. I will try again and report back.

It was really hard to understand exactly what nanomod is, what it does and how to install it as someone that has not messed with android since kitkat. Having to bring myself back up to speed and it is one steep learning curve even to someone that knew android fairly well 4 years ago.
[Magisk] Bludwurst:
Didn't Setialpha change it so rebooting before patching is no longer necessary? Or is that for some Android versions only?

And something not seemingly mentioned, but was the signature spoofing permission granted to MicroG Core (and FakeStore, if used)? Through the App Permission options?

MicroG (and FakeStore) won't ask for them with a big popup like other permissions.
[Magisk] bass@89:
These are the steps I followed as suggested by [MENTION=4187311]Setialpha[/MENTION] & [MENTION=7408621]noc.jfcbs[/MENTION] in earlier posts.

Through the app permission only if system has signature spoof is supported by the ROM itself. Otherwise have to follow those steps for signature spoof patcher.

---------- Post added at 02:51 PM ---------- Previous post was at 02:30 PM ----------

Yes try with this steps.

Don't select "SIG spoof UI to developer options" in during setup wizard. Else patcher flashing will get failed...

I hope it will help...:fingers-crossed:
[Magisk] Bludwurst:
Now that I think of it, granting Spoof Package Signature manually might only be needed if you don't use Nanomod's various zips besides the patcher (and thus manually downloaded MicroG et al from FDroid/the official site). I guess the bundled ones will automatically grant themselves the permission (so to speak).

Sorry for the confusion.

(And good luck, [MENTION=4573886]Texas_Ace[/MENTION])
[Magisk] bass@89:
Yes I already given those said permissions. However gmail app not opening.

I tried another workaround by installing "Inbox by Gmail". After this gmail is working good now and I uninstalled " Inbox by Gmail" too.

I guess there is some syncing issues with gmail and google account setup.

Thanks for suggestions [MENTION=4187311]Setialpha[/MENTION].
[Magisk] kurtn:
Yes. [MENTION=1767226]setia[/MENTION]lpa has made good progress with the patcher. One change: it can patch settings to make spoofing switchable. Its a global setting, not per app.
[Magisk] Max Line:
I did grant all of the permissions. The issue is that its not letting me log in with my own account. I can log in using other accounts. I can how ever log into the normal google play that's running with the google play services.

How do I get the log cat for phonesky and microg?
[Magisk] Oswald Boelcke:
I can confirm that it's no longer required to boot once into system before the patcher is flashed. Since the changes to the patcher a few weeks (or days) ago, you can flash the patcher immediately after your desired Nanomod package (full or microG) and independently if Magisk is used or not. The patcher "creates" the required dalvik and cache now.

Just today, I reverted from RR-N to RR-M - now without Magisk but Chainfire's SuperSU v2.76. It was a clean flash including custom kernel and SuperSU. Afterwards flash nanomod-microG v14.4 and immediately the patcher v14.4 without an issue.

The "spoofing switch" doesn't work with all ROM by my observations e.g. it doesn't with my RR.
[Magisk] hungvip2001:
[MENTION=4187311]Setialpha[/MENTION]

I updated logs. (2) logs are after installation of nanomod
[Magisk] Texas_Ace:
What are these permissions people are talking about? Root permissions? Those are the only permissions I know of, if there some kind of hidden menu for the spoofer?
[Magisk] bass@89:
[MENTION=7408621]noc.jfcbs[/MENTION]

Thanks for the confirmation. I didn't tried while flashing another ROM.

I was trying to help him to overcome his error of signature spoof.

Edit:

Yes it is working. [MENTION=7408621]noc.jfcbs[/MENTION] is correct.

No need to reboot for flashing patcher.

It can be flashed along with clean flash and nanomod flashing.
[Magisk] Bludwurst:
App permissions. Like camera access, contacts, storage, etc.

The spoofing patch adds a new "spoof package signature" permission that can be granted or ...un-granted... at will.

It should be somewhere on Android's default settings app (under, well, app settings).
[Magisk] Texas_Ace:
Oh, so you can control the app permissions directly now in android? Interesting, I used to use Xprivacy to do that.

How does the built in app permissions compare to x-privacy? And/or are there any good xprivacy type apps for 7.1?

Off topic I know but a quick point in the right direction would be great.

Like I said, have not touched android since kitkat so I am playing a lot of catch up.
[Magisk] kurtn:
Yes we have per APP permissions. Spoofing permission only in ROMs with microG support
[Magisk] Texas_Ace:
Interesting, I will be sure to look at that when I mess with the phone again. Still using kitkat as my daily driver until I get this new phone running stable.
[Magisk] Bludwurst:
Xprivacy will always be more elaborate than Android's defaults (it allows spoofing a bunch of info about the phone, doesn't it? [As you can see, I never used it myself]), but installed apps — usually — will manually ask for permissions once run them at first. Permissions can be denied or granted, and modified later if you have second thoughts.

(Although some are silly and don't manually ask for them. In particular, MicroG doesn't outright do it; there's a button to trigger the permission popups manually)

Makes it more obvious when, say, that weird calculator you downloaded wants to access your contacts for perfectly innocent reasons.

Xprivacy alternatives can be Xprivacy itself. Isn't there an official Nougat version of Xposed now?

Or am I thinking about something else?

More on topic, some apps with MicroG will require having their proper permissions set manually to work correctly, because Reasons. Chrome I believe needs Contacts to sync properly, and so does Gmail.

Take a look through this thread and MicroG's if you need more help.
[Magisk] Texas_Ace:
Thanks for the tips, I will look into that when I work on the phone again. Never really ventured into the settings menu yet.

There is an xposed for 7.1, I have just not looked into if xprivacy still works on it, another thing to add to the todo list.
[Magisk] Keule-Tm:
Yes, since Marshmallow it's possible. It's way less sophisticated, though. The sorry point for xPrivacy is: development has stopped (2014, iirc).

Today, there is "Protect My Privacy", developed by the Carnegy Mellon University. It's better than the inbuilt privacy thing, and.. just different from xPrivacy. More up to date (security and design wise).
[Magisk] Texas_Ace:
I will look into Protect My Privacy, I noticed xprivacy stopped so I assumed it didn't work anymore.
[Magisk] krish@3T:
does google search app works ?

if so how to....

for me its keeep closing
[Magisk] bass@89:
Is it possible to install debloated apps alone?

Thanks
[Magisk] Bracher:
I have XPrivacy together with AFWall+ on my Note 3 with the new XPosed - not the Magisk Module (LineageOS 14.1, Magisk 14, Nanomod microG and Nanomod Patcher) and everything works well. XPrivacy is much more detailed than Privacy Guard and it works reliable. I have some doubts about 'Protect my Privacy' as it is not open source so I never used it.
[Magisk] Texas_Ace:
Good to know I will check into that. Although are there new permissions that xpriacy doesn't know about out now that are worrisome?

I agree, protect my privacy not being open source is very concerning. Open source is the first rule for any privacy related program.
[Magisk] Oswald Boelcke:
OT due to the recent posts regarding XPrivacy...

I experienced crashes of applications (for me mainly Nova Launcher) while running RR-N-v5.8.5 with Xposed (didn't matter if rovo89's official framework for Nougat or the unofficial one; however, the fisr one was worse) but I was able to drag it down that Xposed eventually was throttling my engine up into afterburner (or for our British friends "reheat"), CPU always on max, and the device heating up to allow frying of eggs. There wasn't any resources left for other applications to function.

Despite having been pretty happy with RR-N, I reverted to RR-M beginning of the week also for above mentioned reason; however, primary reason was M66B doubts that his XPrivacy is able to ensure privacy on Nougat, and he as the dev will know. By my own observations, I share these doubts. Remembering how Xprivacy worked in the past up to MM, observing it again since Monday and comparing that with my observations of XPrivacy with Xposed on Nougat, I doubt that XPrivacy really protects privacy on Nougat.

...and what's a real pity there is no alternative to XPrivacy available for Nougat, really none. And certainly not "Protect My Privacy", which seems to receive ongoing development for iOS but that obviously terminated for Android years ago.

Again, I apologise for OT.
[Magisk] Lucidioebb:
How can i update Play Store? I read on changelog page that it can be updated manually. Also, how can i update nanomod? its necessary to reflash everything again?
[Magisk] hungvip2001:
Download the last zip and flash over the older. No need to clean flash. And Play store will auto update
[Magisk] Bracher:
Hello I have a question, my devices are running on LineageOS 14.1 so I get regularly updates (nightlies but in fact its weeklies). I've read the whole thread carefully but still one question is it really necessary to make a clean installation when I'm updating my LineageOS. It will take a lot of time, but I suppose I'll have to do it in future, than I'll have to check the changelog to see if it's a major update or if I can wait for the next nightlies. But as I said I'm not sure and perhaps somebodey can give me an advice.
[Magisk] kurtn:
If you have gapps installed, best way to remove is a clean install. For every other purpose a dirty update should do. Favourably through built in updater.
[Magisk] Bracher:
Thank you, I have LineageOS without gapps but with Nanomod microG 14.4 and Nanomod Patcher 14.4 and Magisk 14 - everthing works well and I'm very thankfull for this possibility!!!

But I was wondering if I have to reinstall Magisk, Nanomod microG and Nanomod Patcher after an update - and if so, can I do it without reboot in system in between because in that case I suppose the apps who depend on GCM push notifications would have to be freshly installed which means nearly a clean update
[Magisk] demonoidmaster:
Nope, if you installed nanomod as a magisk module you're good, just make sure you reflash magisk after any rom update you make (that's if the magisk addon.d script doesn't kick in post rom install, which what it does is that it'll autoreflash magisk after any rom update you do)
[Magisk] krish@3T:
Anyone ?
[Magisk] Setialpha:
Dunno, never used it, all permissions granted? Logcat?
[Magisk] Setialpha:
14.5

Version 14.5 is now available. Changes since 14.4:

* General Changes
* Full, microG packages:
* make `sed` shut up when `nanomod-overlay -[A|C|L|R]` is called for the first time
* add `novl` script as shortcut for `nanomod-overlay` script
* Full package:
* switch from APK Mirror build to F-Droid build for Kernel Adiutor
* Full, microG, F-Droid, Uninstaller, Framework-Patcher package, Framework-Patcher addon.d, force-debloat script, nanomod-overlay script
* no longer support `/persist` as location for configuration files
* Updates (manual)
* Play Store (8.3.43.U)
* Updates (automatic)
* (Simple) Calendar (2.8.2)
* F-Droid (1.0)
* Twidere (3.7.1)
* Yalp Store (0.28)

In case of errors, please provide

your device's architecture

your device's Android version (not ROM version)

whether installed as Magisk Module or in System Mode

used Magisk version

recovery.log or logcat or both (whatever is applicable)
[Magisk] kurtn:
Any chance to see improvement in patching Oreo?
[Magisk] Kjivar:
It does work with Oreo? Tested successfully with 4 different builds since 14.3.
[Magisk] silentvisitor:
[MENTION=4187311]Setialpha[/MENTION]

Hello, how are you ! :)

Patcher failed to patch with following error :

*******************************
NanoMod 14.4.20171014
created by @Nanolx
Framework Patcher
Powered by DexPatcher (@lanchon)
********************************

> preparing environment
Archive: /sdcard/ADM/NanoMod-patcher-14.4.20171014.zip
creating: dexpatcher/
inflating: dexpatcher/dexpatcher.dex
inflating: dexpatcher/file.arm
inflating: dexpatcher/file.x86
inflating: dexpatcher/magic.mgc
inflating: dexpatcher/zip.arm
inflating: dexpatcher/zip.x86
inflating: dexpatcher/core_services.jar.dex
inflating: dexpatcher/ui_4.1-6.0_Settings.apk.dex
inflating: dexpatcher/ui_4.1-6.0_services.jar.dex
inflating: dexpatcher/ui_7.0-8.0_Settings.apk.dex
inflating: dexpatcher/ui_7.0-8.0_services.jar.dex
inflating: dexpatcher/hook_7.0-8.0_services.jar.dex
inflating: dexpatcher/hook_4.1-6.0_services.jar.dex
inflating: dexpatcher/75-nanomodpatcher.sh
creating: META-INF/
creating: META-INF/com/
creating: META-INF/com/google/
creating: META-INF/com/google/android/
inflating: META-INF/com/google/android/updater-script
inflating: META-INF/com/google/android/update-binary
inflating: README.md
inflating: ChangeLog.md
> Android 7.0 - 8.0 (SDK 26) detected
> device architecture: arm
> DalvikVM bitness: 64-bit

> patching signature spoofing support

>> patching services.jar
CANNOT LINK EXECUTABLE "/system/bin/patchoat": "/system/lib64/libbase.so" is 64-bit instead of 32-bit
libc: CANNOT LINK EXECUTABLE "/system/bin/patchoat": "/system/lib64/libbase.so" is 64-bit instead of 32-bit
libc: Fatal signal 6 (SIGABRT), code -6 in tid 505 (patchoat)
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
info: read '/dev/tmp/NanoModPatcher/dexpatcher/services.jar'
fatal: exception: lanchon.multidexlib2.EmptyMultiDexContainerException: /dev/tmp/NanoModPatcher/dexpatcher/services.jar
!! failed to apply patches
Updater process ended with ERROR: 1
I:Install took 141 second(s).
Error installing zip file '/sdcard/ADM/NanoMod-patcher-14.4.20171014.zip'

Kindly fix or suggest.

Thank you :good:
[Magisk] Bludwurst:
I think they mean making it faster (some folks say it's slower than in Nougat ROMs).
[Magisk] Kjivar:
Ah, ok. I see. Thanks for clearing that out ?
[Magisk] :
Good day everyone! I'm very new to this Mod and just asking if I've done the process of installing correctly.

- Flashed ROM

- Magisk

- microG

- reboot system

- reboot to recovery

- flash patcher

- flash fdroid

- reboot system

- installed google contacts sync

So far, I have yet to encounter errors but I missed the System Wizard file. Does it matter that I didn't do that step (flashing setup wizard)?

Thanks guys, sorry for this concern. I just want to know if i missed something in the process.
[Magisk] shadowbone:
You don't need the setup wizard as long as your are not using the nanomod complete package. The full package has apps as mentioned in the op, which may or may not be required by you. In that case use the setup wizard to choose which apps you need to get installed in your device.
[Magisk] totalcmdext:
Problem with odex 5.0.1 ROM

I have the following problem with NanoMod-microG-14.x.xxxx

If i flashed via TWRP with the default settings (with Play store) everything is working properly and the Location services run properly.

If i flshed via TWRP with the Yalp Store (nanomod_play 2) then every time the Location services try to used the device restarting.

If i flashed the Play store and then unistall and then istall Yalp store then everything is working fine.

So, there is something in Play store option of NanoMod-microG that not included in the Yalp option.

Any advice?
[Magisk] Oswald Boelcke:
That looked really good. Unless you want to alter the default installation you don't require to create a .nanomod-setup file. This file can be (easily) manually created but also (even more easily) via the Nanomod-setup-wizard.

Additionaly remark: Since a very few versions, it's no longer required to reboot into system after flashing of the desired Nanomod-modules. The patcher can be immediately flashed afterwards.

You stated: "Problem with odex 5.0.1 ROM" (just repeating your post title as XDA labs users can't see this title). Which odexed ROM are you using? Is this ROM supporting signature spoofing, or how did you enable signature spoofing?

Glad to hear that Google PS is properly working; however, but I actually don't know if your issue is really related that you're using an odexed ROM, allow me to quote the Nanomod Readme:
[Magisk] totalcmdext:
This solution is only for odexed ROM

1. Install the latest version of Material Design Xposed Installer (https://xdaforums.com/xpo...aller-t3137758)

2. Inside the Material Design Xposed Installer select Systemless tab and install the appropiate xposed SDK

3. Install the module FakeGapps from Material Design Xposed Installer

4. Install the module XposedGmsCoreUnifiedNlp from Material Design Xposed Installer
[Magisk] Primokorn:
My custom ROM supports signature spoofing and I use my own script to install microG and other packages.

Can I grab your modded version of Google Play to fix FCs with in-app purchases? Or is it dependent on other stuff?
[Magisk] Texas_Ace:
Nanomod 14.5 seems to be working good for me now as a system install (magisk causes bootloops).

Only issue I am having is microG will not spoof safetynet. Is this working? Do I need to use a 3rd party server?

Where is droidguard installed now? Some searching showed that moving it to /system/priv-app/ can fix the issue in some cases.
[Magisk] kmem:
Can anyone confirm this works on a secondary ROM using Multirom? I followed the requisite installation instructions but it doesn't appear to install. Tried using magisk 14.0 and 14.3 to no avail. Only Microg droidGuard helper winds up getting installed for some reason. I used vanilla Microg with multirom several months ago without issue.
[Magisk] silentvisitor:
Hello [MENTION=4187311]Setialpha[/MENTION] [MENTION=7408621]noc.jfcbs[/MENTION] [MENTION=279681]totalcmdext[/MENTION]

Please help me run MicroG on my device.

OnePlus 3

SD821 arm64

Validus Oreo

SDK 26

*******************************
NanoMod 14.5.20171022
created by @Nanolx
Framework Patcher
Powered by DexPatcher (@lanchon)
********************************

> preparing environment
> Android 7.0 - 8.0 (SDK 26) detected
> device architecture: arm
> DalvikVM bitness: 64-bit

> patching signature spoofing support

>> patching services.jar
CANNOT LINK EXECUTABLE "/system/bin/patchoat": "/system/lib64/libbase.so" is 64-bit instead of 32-bit
libc: CANNOT LINK EXECUTABLE "/system/bin/patchoat": "/system/lib64/libbase.so" is 64-bit instead of 32-bit
libc: Fatal signal 6 (SIGABRT), code -6 in tid 534 (patchoat)
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 25
info: read '/dev/tmp/NanoModPatcher/dexpatcher/services.jar'
fatal: exception: lanchon.multidexlib2.EmptyMultiDexContainerException: /dev/tmp/NanoModPatcher/dexpatcher/services.jar
!! failed to apply patches
Updater process ended with ERROR: 1
I:Install took 132 second(s).
Error installing zip file '/sdcard/ADM/NanoMod-patcher-14.5.20171022.zip'

Thank you so much !
[Magisk] Setialpha:
microG does not aid in passing SafetyNet, only Magisk does.

I'll have a look.
[Magisk] Shadow53:
I've used it for myself with vanilla microG while purchasing an app on the Play Store. At least, I'm 95% certain it was vanilla microG. If you use the patched Play Store, you'll need to manually grant it signature spoofing permissions.

If it makes things easier, I provide standalone zip files for installing the Play Store (official and patched) at https://shadow53.com/android/downloads/#google-play-store-standalone with instructions on granting signature spoofing at https://shadow53.com/android/no-gapps/faq/playstore-incorrect-signature/

(Note: I'm sometimes a little behind in updating to the newest version, so I think the one on my website is a version behind)
[Magisk] krish@3T:
[MENTION=4187311]Setialpha[/MENTION]

Log gor Google search fc

Rom validus oreo

Device 3T

Tried both beta and stable
[Magisk] silentvisitor:
Have you got MicroG running on your setup?
[Magisk] krish@3T:
No problem apart from the Google search (very nifty to answer mcq in class test :silly:)
[Magisk] demonoidmaster:
Just do what you did first (with play store) if that works and install yalp as a normal app post boot, either ways it finds updates for itself when there are some

Either ways i see no reason to grant location detection to the play store or yalp
[Magisk] _Kosmas_:
Validus Oreo has signature spoofing in built! No need to run the Nanomod Patcher ;).
[Magisk] Bludwurst:
Yalp Store doesn't ask for location.
[Magisk] silentvisitor:
Yeah, was brought to my attention yesterday :)

Thanks !