yashsingh1/xdaforums huggingface dataset:
[Magisk] Oswald Boelcke:
Google Play Store i.e. the Phonesky.apk is coming with Nanomod-mircroG if enabled (not sure but I believe it's even the default, otherwise you need to use the setup.zip first and select in Aroma the Play Store or you create the setup yourself).

Second choice: Try this. I hopefully explained well enough.
[Magisk] Setialpha:
Patcher 13.1~beta5

OK. So the fifth beta of the new patcher is now available. Highlight since last beta:

addon.d support

updated patches to latest versions

try SecSettings.apk if Settings.apk is abscent

a few minor fixes

Full ChangeLog since 13.0:

* Framework-Patcher package:
* update `dexpatcher` to 1.3.1
* remove unused dexpatcher.jar file
* no longer requires booting into ROM before patching
* more reliably catch `dexpatcher` errors
* patching signature spoofing UI now supports
* LineageOS/AOSP Settings.apk
* Samsung TouchWiz SecSettings.apk
* update to use Magisk v13 functions when Magisk is utilized
* do all `dexpatcher` operations in `BASEDIR`, not `TMPDIR`
* clean-up environment before doing anything
* update to new Haystack patches
* addon.d support (auto repatch after ROM update)

Please test and report back any issues.
[Magisk] hungvip2001:
Any way to use NanoMod with odex ROM ?
[Magisk] Setialpha:
NanoMod? Yes. The Patcher? No, technically not possible.

You can, however, deodex the ROM yourself, either completely or only the framework files ...

Or, if you're on Marshmallow or below, use the FakeGApps Xposed Module.
[Magisk] kurtn:
Flash patcher all works well. Addond gets created and working. Signature spoofing after LOS update not checked. Log of manual flash attached
[Magisk] Setialpha:
Patcher 13.1~beta6

The sixth beta fixes an issue regarding core_services.jar patching for addon.d (discovered in [MENTION=8031265]kurtn[/MENTION] recovery.log).

How to get addon.d setup on clean flash of ROM:

- simply flash NanoMod-Patcher normally, it will install it's addon.d

How to get addon.d setup when already using NanoMod/dirty flash of ROM:

- for

Magisk Mode

: remove /system/.nanomod-patcher and then flash the Patcher

- for

System Mode

: mv /sdcard/services.jar to /system/framework/ (/sdcard/services.jar is the backup file the patcher creates), next remove /system/.nanomod-patcher and then flash the Patcher

Please test and report back any issues.

Edit: also updated the Uninstaller to remove NanoMod-Patcher addon.d environment, the documentation has also been updated.
[Magisk] Setialpha:
13.1~beta7

Sorry, but already at beta7. Changes since previous post (lol):

install addon.d even if /system/.nanomod-patcher exists

addon.d exits, if it's support files in /data/nanomod.patcher don't exist

So that means: regardless if the ROM is already patched or not, simply flash the Patcher. It will either patch the ROM and install it's addon.d OR only install it's addon.d if the ROM is already patched.

Please test and report back.
[Magisk] kurtn:
Whow! Not so fast! I'm just clean flashing beta 6.

---------- Post added at 01:45 PM ---------- Previous post was at 01:29 PM ----------

Beta 6 is OK when dirty flashing LOS. Next test: use LOS updater.

---------- Post added at 02:09 PM ---------- Previous post was at 01:45 PM ----------

LOS updater OK. Next test: setup system with official patcher and flash beta 7.
[Magisk] kurtn:
Somehow it doesn't work for me, when flashing over nanomod 13.1 beta 2. But is this necessary? Beta 6/7 is for people who regularly update by dirty flashing. After such an update simply flash patcher 13.2 - finished.
[Magisk] Setialpha:
What doesn't work? The Patcher itself? addon.d?
[Magisk] kurtn:
Beta 7 pretend it created add-on.d I didn't check. Dirty flashing didn't start patcher.
[Magisk] Setialpha:
OK, need to re-check.
[Magisk] Setialpha:
13.1~beta8

So the last beta for today..., fixes an issue in addon.d installation.
[Magisk] demonoidmaster:
We live fast ?
[Magisk] digitman xxx:
for me run custom RR-Marshmallow 6.0.1 Unrooted on my old samsung sm-g7102 wanna try using it with miroG but without xposed, so tried patching it with another tool Tingle(SignSpoof patch file on PC by ADB assist). Unfortunately faced Error: No dex file(s) found, probably the rom is odexed. post here and yes got the same answer above. anyway said i'll give Nanomod-Patcher a try then see. Clean flash rom+ Patcher 13.1~beta3 and .nanomod-setup on Ext Card with value"1" for both forcesystem and sigspoofui and yup working flawlessly. That mean could patching sign spoofing on Odex rom by Nanomod-patche, at least my odexed rom. Thanks [MENTION=4187311]Setialpha[/MENTION]
[Magisk] Setialpha:
I doubt that RR is odexed, it's an LOS/AOSP based ROM. Have been using it for long time. Maybe it's a bug in [MENTION=5627087]ale5000[/MENTION] Tingle?

In fact AOSPA is the only odexed after market ROM *I* am aware of.

Stock ROMs are basically always odexed, Modded Stock ROMs so-so.
[Magisk] zeeBomb:
I'm having issues with my wifi connection keep going away every now and then. Is it my location? My connection is pretty strong too.
[Magisk] kurtn:
Sorry, agin no good news.

Made a clean install with LineageOS+addonsu; booted; flashed patcher 13.1 beta2 and shadow53's microg.

Here is the log of dirty falshing beta8 and a lineage update: Patcher did not start.
[Magisk] Setialpha:
Uff, I'm stupid. I'll fix it today evening.
[Magisk] ydd0ras:
Hello Setialpha,

just want to thank you for your work. Life is much better (for me!) w/ the "real google" stuff. I had never any problems with microG/Nanomod and other stuff on my OPO and Xiaomi Mi4. Hope one day i can patch my Oreo custom ROM as well (AOSP on my Mi4).

Grüßle aus Stuttgart!

Cheers!
[Magisk] Setialpha:
Patcher 13.1~beta9

So the (hopefully) last beta of the new patcher is now available.

Includes fixes regarding addon.d installation and also makes configuration variable fallback definition more robust.

Please test and report any issues.

Ah, while we're at it, anyone in charge of a services.jar from Oreo?
[Magisk] kurtn:
Yea! Beta 9 does the the job. Instead of flashing the patcher after dirty ROM update, we now can flash beta 9 at any time. No more re-flashing after ROM update.
[Magisk] Shadow53:
Sadly my phone (Nexus 6) is one generation too old to get the Oreo update, but depending on what you are looking for, couldn't you could check the source code or extract the services.jar file from a Google factory image?
[Magisk] Setialpha:
Of course, but I was just asking (I tried to be lazy).
[Magisk] Setialpha:
13.1

NanoMod 13.1 is now available. Highlights since 13.0

Google Sync Adapters for LL are now 5.0

reboot-less Framework Patcher with addon.d support

no longer required to boot into ROM once

addon.d script that re-patches ROM after update

NanoMod currently is not compatible with Magisk 13.5/13.6 beta (already reported)

possible work-arounds:

stay at Magisk 13.3

install in System Mode

Full ChangeLog since 13.0:

13.1.20170829
* Bug Fixes
* F-Droid package:
* Fix installation issue in `nanomod_libs`
* Full, microG packages:
* Downgrade Google Sync Adapters for LL to 5.0
* General Changes:
* Framework-Patcher package:
* update `dexpatcher` to 1.3.1
* remove unused dexpatcher.jar file
* no longer requires booting into ROM before patching
* more reliably catch `dexpatcher` errors
* patching signature spoofing UI now supports
* LineageOS/AOSP Settings.apk
* Samsung TouchWiz SecSettings.apk
* update to use Magisk v13 functions when Magisk is utilized
* do all `dexpatcher` operations in `BASEDIR`, not `TMPDIR`
* clean-up environment before doing anything
* update to new Haystack patches
* addon.d support (auto repatch after ROM update)
* on-pc Framework-Patcher script:
* exit if not in TWRP immediately, not late in process
* add `--gui` parameter to patch Signature Spoofing toggle in UI
* clean-up previously patched files on start (if any)
* build-package:
* add `dalvik` option, prepares a jar file for use with DalvikVM
* Uninstaller:
* also remove Framework-Patcher addon.d upon uninstallation
* Updates
* Play Store (8.1.73.S)
* Substratum (823)
* Amaze (3.2.1)
* Yalp Store (0.23)
* Kernel Adiutor (0.9.72)
* Simple Gallery (2.13.1)
* Lightning (4.5.1+snapshot20170813)
* Open Camera (1.40)

The documentation has been updated, aswell.

Download from AFH.

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] ydd0ras:
I would do that for you for sure but I think this is a bit too difficult for a noob. [emoji25]
[Magisk] Deva Kaushik:
Im using Jaguar ROM ZUk Z2 plus. First the earlier version worked perfectly, but when i installed latest Nanomod MicroG the playstore crashes very often even after enabling all security checks.

MicroG 13.0 works and 13.1 does not work
[Magisk] 1plus:
[MENTION=4187311]Setialpha[/MENTION]

Just installed the new version -- very nice indeed, the patcher works straight away, no need to boot ROM first.

Still, two minor issues persist -- Orfox continues to force close on start every time and also I'm unable to place any widgets in the launcher -- Settings crash (not sure why settings specifically).

Are you able to add widgets yourself?
[Magisk] Setialpha:
No log, no solution...

Orfox works here, adding widgets aswell.

No log, no solution...
[Magisk] Deva Kaushik:
How to get a log?
[Magisk] Setialpha:
Many howtos here, for example https://xdaforums.com/showthread.php?t=1726238
[Magisk] Deva Kaushik:
Anyways I have reverted back to 13.0 and its working fine, do you suggest me to get 13.1?
[Magisk] Setialpha:
The only thing that changed in the microG package is Play and Yalp Store, so it doesn't actuallly matter.
[Magisk] K3V1991:
The NanoMod Patcher does not install

LG G6 (H870)
[Magisk] demonoidmaster:
Knowing XDA ya know someone out there will make stock builds or custom roms for your phone model

---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------

*sigh* flash it in twrp
[Magisk] K3V1991:
Does Not Work :rolleyes:

I'm in Fulmics 1.6
[Magisk] demonoidmaster:
Then post your logs
[Magisk] K3V1991:
No Log but a screen
[Magisk] Oswald Boelcke:
TWRP log is usually available at root/tmp but you can also very easily copy it to SD. Just go in TWRP to "advanced" then "copy". Screenshots might augment a report but only logs really help.

Just by a view onto your SS, I'd personally do the following:

- Unless already available download Magisk Uninstaller and Magisk v13.3

- Boot into TWRP (don't try to use Magisk Manager for the following steps)

- Take your Nandroid backup

- Flash Magisk Uninstaller.zip

- Flash Magisk v13.3

- Boot into system and check if root and Magisk are correctly available

- Boot into TWRP

- Flash the Nanomod module of your desire (if prefered the setup-wizard before this)

- Flash the Nanomod-patcher

- Reboot into system and enjoy starting with the setup of microG

- Don't forget to grant all required permissions to microG and to the backends of your desire.
[Magisk] Gonzalez92105:
I have an issue. No matter if I flash microG from magisk, or through twrp it never boots up into the system. This is the procedure that I do. Clean wipe v

---------- Post added at 05:25 AM ---------- Previous post was at 05:17 AM ----------

Interesting. My entire text didn't post. Basically, whenever I flash microG it never boots up into the system. No boot animation occurs, and boots into twrp by itself. I clean flashed rom, magisk, and boot up into the system. After that I flash the patcher in magisk, or twrp. Same with microG, I've tried flashing through twrp, and magisk, but with the same result. I've never had this issue previously on the same rom with the same steps. Currently on htc 10, latest twrp, latest firmware, and tried the latest patcher and microG on purefusion. How can I send a log towards your way? Thanks.
[Magisk] Setialpha:
I've linked a logcat tutorial a few posts ago, read one post back for twrp log.

As mentioned in the announcement post and the first post: NanoMod is not compatible with Magisk 13.5/13.6, just in case you're not on 13.3.
[Magisk] Gonzalez92105:
Thank you for pointing me out to the tutorial, I'll check up on it. I'm aware of the magisk betas not working properly, that wasn't the case this time. I haven't been on this thread for awhile. Thought the procedure on how to get this up, and working changed. It's strange though, I just tried it on my lg g3 and didn't have any issues right now. Perhaps the rom got altered slightly causing this issue to occur now. Thank you once again.
[Magisk] Ophidian_DarkCore:
If you have access to a linux box, use tingle https://github.com/ale5000-git/tingle the patcher hasnt worked for me in a lonnnng time too, fails on hooking or something
[Magisk] ShapeShifter499:
[MENTION=4187311]Setialpha[/MENTION] The patcher is failing in TWRP but it succeeds in Magisk Manager, attached is the recovery.log. Seems like it can't make use of 32 bit on 64 bit or something of the such. It also causes /system/bin/sh to crash. 'adb shell' and flashing other stuff after this patcher also fails until I reboot TWRP.

My System Setup

Moto X Pure

LineageOS Nightly 08/28/2017

TWRP 3.1.1-0

NanoMod 13.1.20170829

NanoMod Patcher 13.1.20170829

Magisk 13.3
[Magisk] K3V1991:
Okay i think it worked with Tingle :D

Edit: Yes!
[Magisk] Islam Mu:
microG support arm64 roms ?
[Magisk] Oswald Boelcke:
Yes, as long as the ROMs support signature spoofing.
[Magisk] Setialpha:
patcher 13.2~beta1

Given the bug reports (well, those that actually were bug reports, including proper description and logs): here's a new beta build of the Patcher. Changes since 13.1:

* Bug Fixes
* Framework-Patcher package, Framework-Patcher addon.d:
* include 32 bit paths in `${LD_LIBRARY_PATH}` on 64 bit devices
* change the way `${LD_LIBRARY_PATH}` is used, internally
* put ROM paths before TWRP paths in `${PATH}`
* other minor fixes

please test and report any issues.

[MENTION=2022267]ShapeShifter499[/MENTION]
[Magisk] kirkirehani93:
Still in need of services.jar from Oreo?
[Magisk] Setialpha:
Patcher 13.2 beta2

Patcher 13.2-beta2 is now here. I've successfully tested that Nougat patches still work on Oreo, so the restriction for SDK 26 was removed. In case anyone uses de-odexed Oreo ROM already, you may give it a try.

The framework-patcher PC script was updated, accordingly and I've informed the Haystack developer.

Feel free to test and report any issues.

______________

On a side-note: nothing against the freedom of choice (I love choice and openness!), but NanoMod has a

on-pc

patcher aswell (as stated in first post), so feel free to try it. Just as the on-device patcher it uses Haystack (which uses the awesome dexpatcher). While the end-user result might be the same as using Needle/Tingle, dexpatcher is technically lightyears ahead of Needle/Tingle. Also only Haystack includes the patch for adding in a toggle into Developer Settings.

______________

[MENTION=4950447]kirkirehani93[/MENTION] thanks, already got my hands on it.
[Magisk] kirkirehani93:
Thanks mate will try and update
[Magisk] evilvoice:
[MODULE/SYSTEM-MODE] NanoMod 13.1.20170829 (microG, pseudo-debloat, F-Droid + apps)

This needs to be said so much more. If you're going to patch on PC, you might as well use this or Haystack for the added features and enhancements.
[Magisk] kirkirehani93:
[MENTION=4187311]Setialpha[/MENTION] The latest beta patcher fails on preparing environment

Twrp 3.1.1.0
[Magisk] Setialpha:
I'll do some tests tomorrow, but recovery.log would be nice.
[Magisk] kirkirehani93:
There you go

https://pastebin.com/SDMBTNed
[Magisk] Setialpha:
patcher 13.2-beta3

Patcher 13.2-beta3 with the following fixes:

change PATH after LD_LIBRARY_PATH was set, not before

fixup installing addon.d for Android 7.0 - 8.0

Please test and report any issues.

[MENTION=4950447]kirkirehani93[/MENTION]
[Magisk] m_reyna_16:
hello, I am running latest stable version of nanomod. I have a oneplus3 using vertex rom with signature spoofing enabled.

my problem is that google play services keeps crashing after i reboot my phone. google play works fine after i delete cache and data, remove the account and reboot and set it up again. I installed nanomod micro g using magisk 13.3 stable. anybody having this issue?
[Magisk] Setialpha:
What crashes (microG is a replacement for Play Services, so they are not installed)? When does it crash? Also see the known Issues https://gitlab.com/Nanolx/NanoMod#issues
[Magisk] m_reyna_16:
yea im aware of the known issues, as a matter of fact i had the webpage open and was going one by one on the known issues list to see if i dont have them.

safetynet failed so i installed droidguard.apk as a user app just like in issue number one. that fixed issue one and two. after that everything works flawlessly until i reboot the phone, play store crashes until i delete cache and data in the settings. and again everything works well until i reboot the phone and same problem persists until i do the same thing all over

note: by me saying "everything works" i mean i dont get to test contacts sync. i dont get to set that up because im still trying to configure the play store to work correctly
[Magisk] demonoidmaster:
You have this installed to system or as a magisk module? If it's to system, copy the playstore apk from system and uninstall it then install the playstore apk as a normal user app. Might help
[Magisk] m_reyna_16:
I installed this using the magisk manager
[Magisk] demonoidmaster:
Ok then i guess configure the setup wizard to not install play store when you run the nanomod installer

Then after that you won't have the Play Store until you install it, if you'd want the lastest version go to apkmirror and dl it and install
[Magisk] fir1996:
Help

Getting "error retrieving information from server [RH-01]" [MENTION=4187311]Setialpha[/MENTION] I am using lineage os 14.1 I have try clearing cash, DAT, reboot every thing nothing works any help would be appreciated

Note : I have install nanomod patcher + nanomod micro g
[Magisk] ShapeShifter499:
Install play services and the play store as a user app, that is a work around I've used. For the longest time only droid guard needed to be installed as a user app but that seems to have changed with NanoMod 13.1.20170829 Maybe it's a MicroG issue, I'm not sure.
[Magisk] ShapeShifter499:
I booted into TWRP and deleted the patched files and tried the patcher again.

13.2-beta1 and beta2 fails with a "failed to mount data" (which is odd, isn't it already mounted for TWRP?) and 13.2-beta3 fails mounting magisk.img Attached are the recovery.log from all the attempts.

My System Setup

Moto X Pure

LineageOS Nightly 08/28/2017

TWRP 3.1.1-0

NanoMod 13.1.20170829

NanoMod Patcher 13.2.beta1, 13.2-beta2, and 13.2-beta3

Magisk 13.3
[Magisk] ShapeShifter499:
I should also add, your "framework-patcher" in the GitHub (which is mirrored from GitLab?) is failing to create a folder '/magisk/NanoMod/system/priv-app/Settings' so it fails to copy over Settings.apk I end up having to create the folder manually before it copies over everything correctly. Here is an attached log from that.
[Magisk] m_reyna_16:
So does contacts sync work on stock aosp messaging app or do I need to install the google contacts app?

---------- Post added at 09:15 PM ---------- Previous post was at 09:03 PM ----------

The play services too? I thought the whole point of microg was to not install play services?
[Magisk] ShapeShifter499:
I meant the MicroG services, install all of the MicroG services as a user app while they are still installed with NanoMod. They will still get the /system/priv-app permissions and not crash. The last time NanoMod stuff crashed it was a issue with Magisk but I thought the bug was fixed.
[Magisk] Setialpha:
Ahhhhhh! Play Store crashes, because it tries to update itself!

Disable the DailyHygiene service of the PlayStore or grab my latest modified version from https://gitlab.com/Nanolx/NanoMod/tree/master/Full/system/priv-app/Phonesky
[Magisk] m_reyna_16:
I figured it had something to do with it... It's just I'm a noob so I couldn't prove it was that! Anyways, how can I disable the daily hygiene service? Pros and cons with disabling it vs using the latest modified one?
[Magisk] ShapeShifter499:
Will that be included in the next version of NanoMod?
[Magisk] Nosepull:
After I tried to install a new ROM and apply the 13.1 NanoMod, I get all the errors as already described (I only use NanoMod patcher). Even worse, now I can not even use an older NanoMod version which had worked previously. Even the old version now gives the strange errors. Only restoring a Nandroid backup helps.

I don't really understand why suddenly also previously working NanoMod versions fail?!?!?
[Magisk] Setialpha:
Of course. That's the link tk the latest version.
[Magisk] m_reyna_16:
So then if I want calendar and contacts sync I have to install the Google apps? Or will the stock aosp ones work?
[Magisk] Setialpha:
Enable sync adapters before installation, which are required for that. Read up Alter Installation in the docs or use the NanoMod setup wizard.
[Magisk] kirkirehani93:
It works!! Though it 30 mins to patch!!! :Victory:
[Magisk] ShapeShifter499:
What the frick is wrong with my device? it doesn't work here lol
[Magisk] kirkirehani93:
It was stuck for me on cleaning files after installation....rebooted...and found spoofing to be enable. It took a very long time....
[Magisk] ShapeShifter499:
It's just failing to mount magisk at all. The beta3 seems to be stuck at 32 bit vs 64 bit again
[Magisk] kirkirehani93:
Try one thing....manually unmount data and system from twrp and try flashing it...
[Magisk] Setialpha:
patcher 13.2-beta4

Ever since the advent of Magisk v13 I occasionally ran into problems regarding magisk.img. So I've reverted back to custom magisk.img handling functions (which are modified pre-Magisk-v13 functions), as they have been used in NanoMod 13 and before. I made a few more changes.

I'm pretty much sure it works now for most (if not, I suggest everyone sending me their devices by air mail, so I can do real-life tests on more than two devices :p) .

Please test and report back.
[Magisk] akoyaxd:
Thank you very much!! I had issues with mounting magisk.img with 13.1 and 13.2beta3. 13.2beta4 works fine now!

Is there a way to donate to you?

Edit:

nvm. found it! ^^

Device:

Oneplus 3t Sultanxda LOS build from 3rd September.
[Magisk] m_reyna_16:
So everything worked as it should... It survived the night without any issues and it even synced...

But now a new problem arose... After I flash magisk modules in recovery, my phone will not boot, it stays stuck on the oneplus logo. The modules I flash are...

-App systemizer

-Viper4arise and the Magisk module

-Enable doze for gms (although I've reflashed the rom to get it working again and reflashed the Magisk modules without this module and problem still happens)

- Greenify4magisk

-iYTB

-Max resolution for YouTube

- 2.5 and 5 wifi channel bonding

-Universal deep buffer remover

Am I missing a setting or doing something I'm not supposed to?
[Magisk] Setialpha:
Dunno, not all modules are compatible with Magisk 13.5/13.6 beta, in case that's what you use. When you use microG, don't use 'doze for gms'. Else maybe the magisk log in /data contains anything?
[Magisk] m_reyna_16:
I'm using 13.3 magisk latest stable. I figured it might give me problems so I tried flashing all the modules except for the doze for gms but same thing happens. The Magisk login data contains anything like what? I didn't fully understand ure question

---------- Post added at 11:45 AM ---------- Previous post was at 11:30 AM ----------

Let me add that I selected the internal memory in the setup wizard... May that be the problem?
[Magisk] Setialpha:
Nope, it just stores configuration files there. Try flashing modules one-by-one, to see which one(s) cause(s) the issue.

Magisk stores a logfile in /data, upload it here, maybe it contains useful infos.
[Magisk] sudokamikaze:
Hi guys!

For now, I'm using latest build

Can I update Google contacts for now?