yashsingh1/xdaforums huggingface dataset:
[Magisk] m_reyna_16:
There wasn't any log file for some reason... So in order for me to try and get one I decided to reflash everything for the 100th time lol

I erased everything even the files on my internal memory but I found out that it wasn't that... It was that I was flashing viper4arise, with the deep buffer remover option selected on the configuration file and then trying to flash the universal deep buffer remover from the Magisk app after that. That caused my phone not to start up... Everything including sync is working now... Only thing I can say that it is wierd is that I would flash the same zips when I was using gapps and never caused any problems. I guess the microg mod is different somehow

Anyways, just wanted to update you on the problem I was having
[Magisk] :
Can you make one for Oreo? I'm testing stable on 1+1 running also 8.0. I have play store working on but patcher is failed.
[Magisk] Setialpha:
Does Patcher 13.2-beta4 not work?
[Magisk] :
My fault my rom is odexed
[Magisk] hungvip2001:
About the uninstaller, what I need to do if I want uninstall a part of this mod( like Yalp Store or the patcher,...) ?
[Magisk] Kjivar:
Wow, thanks alot! This is such a great mod which got even better with the patcher. Not too many ROMs with signature spoofing. Now I can try several others. I do not have the possibility to set up a pc to patch so this is awesome ?
[Magisk] Hurkamurka:
First, thanks [MENTION=4187311]Setialpha[/MENTION] for this great work!

I just wanted to report that everything works fine on a OnePlus One running ResurrectionRemix - v5.6.3 - Marshmallow 6.0.1_r13. Safetynet is good if Xposed magisk module is disabled. Unfortnately V4A magisk module causes bootloop, trying ARISE as abacate123 mentioned, though i have to figure it out how to make it work :) (first time using ARISE).

edit: Audio Modification Library Framework magisk module causes bootloop too.

edit2: ahrion's v4a magisk module causes bootloop too.

Till this time i tried nanomod as magisk module. Now i'm gonna try it as system mode, maybe that's the problem. -->

--> edit3: Force System Mode just worked for me. Trying ARISE as abacate123 mentioned. --> And safety net with xposed magisk module disabled still works well.
[Magisk] Oswald Boelcke:
I think Nanomod is so easy to use. I'd simply uninstall and immediately re-install the desired parts e.g. using the aroma-module for setup prior to flashing of the actual module(s).
[Magisk] m_reyna_16:
PayPal keeps asking me to set the "verify apps" feature but I don't have that option. Is there a workaround for this?
[Magisk] anoukaimee:
This looks great, but wondering if it is compatible with Project Fi? S.i.X ROM has added it as an alternative to GAPPs and I'd love to use it, but installed it and even tho Google Play Services is installed, I get the message that "Project Fi won't run without Google Play Services." ...

I installed the MicroG version per S.i.X. instruction.

Thanks.
[Magisk] Setialpha:
And did you set it up?

https://gitlab.com/Nanolx/NanoMod#microg-1
[Magisk] ydd0ras:
Yeah, the same problem in my Mi4.
[Magisk] uli_p:
I tried to install nano mod on a Razor i XT890 running lineage OS 11 11-20170227-UNOFFICIAL.smi (Android 4.4.4). However the patcher fails. It returns an error 1 saying that it fails to apply hook_4.1-6.0_services.jar.dex. See attached image ans log.
[Magisk] K3V1991:
I tryed to install it on my LG G6 but after Installation it hangs on the bootscreen

How to solve this?
[Magisk] Oswald Boelcke:
You won't receive an earlier or better answer by double posting (the other post is here). I suggest to occasionally but soon digest the forum rules. Links are in my signature block but can also easily retrieved by a search.

All guys who are able to support are certainly monitoring all the respective threads but I know a few who simply decide to wait with a reply in case of double postings.

EDIT: Not necessarily and most likely not related to the device but to the ROM, Magisk version used, installation procedure executed etc. Some more detailed information is appreciated, best including of a TWRP log.
[Magisk] K3V1991:
Device: LG G6 (H870)

ROM: Fulmics 1.6

Magisk v13.3 + Magisk Manager v5.1.1

Installed NanoMod-microG latest Stable release with TWRP 3.1.1-0

Atfer this the Bootscreen freezes
[Magisk] Setialpha:
Look a few posts back for patch 13.2 beta4, it includes several fixes (and will soon™ be officially released).
[Magisk] Oswald Boelcke:
Since end of August you're reporting that it doesn't work with Fulmics 1.6 and still try it.

Here you already got an advice that never was thanked by you or replied:

I just checked the LG G6 Fumics thread, and please allow me to quote from its post #3:

By my logic, if it has a custom Google Apps removing capability the ROM first comes with GApps.

I absolutely concur with marcdw, either completely remove all Google stuff from your current ROM or choose a ROM that doesn't come with Google. I doubt that microG is going to work with Fulmics (in any version) i.e. neither Nanomod will do.
[Magisk] K3V1991:
Whats wrong Dudes?

The patching & installing works..

Info i tryed the manual uninstallation of Google Play Store, Google Play Services & Google Framework..

After this hanging on Bootscreen..

On my LG G3 works all great
[Magisk] Oswald Boelcke:
I very much doubt that I'm your "dude". Don't remember anything we did together so far.

Glad that patching and installation worked, and that your LG G3 is working.

Totally convinced you're going to manage the remaining things.
[Magisk] Setialpha:
13.2.20170906

Version 13.2 is now officially released. Highlights since 13.1

several fixes and improvements in the on-device Framework-Patcher and it's addon.d

Officiallly support SDK 26 / Oreo

If you want to create snapshot builds, read up the new instructions, as it heavily changed.

Full ChangeLog since 13.1:

* Bug Fixes
* Framework-Patcher package, Framework-Patcher addon.d:
* include 32 bit paths in `${LD_LIBRARY_PATH}` on 64 bit devices
* revert back to own magisk.img handling functions
* other minor fixes
* General Changes
* Framework-Patcher package, Framework-Patcher addon.d,
* Framework-Patcher Script:
* Nougat patches also work on Oreo, remove restriction for SDK 26
* Full, microG packages:
* add Oreo Google Sync Adapters (from O DP4)
* Full, microG, F-Droid packages:
* remove most apks from GitLab repository
* instead use `build-package pull` to download latest apks automatically
* a few apks are still in the repo as `build-package` can't (yet) grab them automatically
* a few apks are still in the repo as they are self-built or modified
* thanks to shadow53's `android-zip-builder` [> GitLab](https://gitlab.com/Shadow53/android-zip-builder)
* `build-package` Script
* `build-package` now prefers configuration files from `repo/data` over `repo/doc` during package creation
* `.nanomod-setup`
* `.nanomod-apps`
* `.nanomod-overlay`
* `build-package` now has new switches:
* `build-package pull` to download all required apks for Full, microG and F-Droid package
* `build-package u-microg` to update microG
* `build-package u-fdroid` to update F-Droid
* `build-package u-apps` to update (most) applications
* `build-package u-swipe` to update swipe libraries
* `build-package u-gsync` to update Google Sync Adapters
* `clean` remove any untracked files from the repo (e. g. from `build-package pull`)
* `build-package` script no longer surpresses `zip` error messages
* Documentation:
* updated for recent changes
* minor changes
* Updates
* Yalp Store (0.24)
* Simple Gallery (2.13.4)
* K9-Mail (5.208)
* OpenKeychain (4.6)
* Play Store (8.1.73.S)
* GNU Nano (2.8.7)

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:
Hey guys, maybe someone could help me. I am using microG and Co. nearly 6 months and i don't want going back to gapps. Unfortunately, one of my fav ROMs is now odexed. And here is the dumb question: is there a way to deodex this ROM in order to use the patcher?

Thx!
[Magisk] Oswald Boelcke:
Don't know if this will work as I'm always on the same (deodexed) ROM:

https://xdaforums.com/mi-5/how-to/guide-how-to-microg-mi5-custom-nougat-t3590435
[Magisk] ydd0ras:
Thx, will check that asap. And look here, an Bvb home screen [emoji16]
[Magisk] uli_p:
Strangely enough now I also get an "Error 1"' message when flashing the nano-mod.zip (see the attached screenshot) - even though it had worked the first time that I tried it. I didn't change anything, at least as far as I can remember. I am stuck.

By the way thank you [MENTION=4187311]Setialpha[/MENTION] for this wonderful mod and your incredible support. I have been using it for months on my OP3T.
[Magisk] uli_p:
Sorry-I forgot the Screenshot.
[Magisk] Setialpha:
Need recovery.log to check what's going on.
[Magisk] uli_p:
Sorry. I didn't have access to my Computer when I wrote the message, so I couldn't get the log of the Razr I. Here it is:
[Magisk] Setialpha:
Thanks, I'll have a look.
[Magisk] :
Any news about compatibility with latest Magisk v14?
[Magisk] Setialpha:
13.2a

Version 13.2a is now available. Changes since 13.2:

* Bug Fixes
* Full, microG packages:
* Fix bootloop with Magisk 13.5 / 13.6 / 14.0

In fact the incompatibilities with a handful of other Magisk Modules *should* be fixed aswell, feel free to test.

>> Announcement for 13.2.

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] demonoidmaster:
Chill...
[Magisk] Setialpha:
Yes, 13.2a fixes incompatibility of NanoMod with a few other modules, I've tested with the audiomodlib based modules. Everything fine now, so the longest existing unfixed bug in NanoMod is finally fixed.
[Magisk] Trademark97:
Just wondering, is Nanomod 13.2a supposed to install under Magisk v14.0 in System mode as opposed to as a module? I'm asking because I need the pseudo-debloat feature, and being unable to use that, as it were, would be a blocker for me from moving to the latest Magisk version. I would appreciate help in this matter; if it is a mistake on my end, I would be glad to know. If not, I will, once again, be happy to help find the problem and test its fix(es).

EDIT #1: Pictures added for proof
[Magisk] Setialpha:
Unless you explicitely tell* the installer to do system mode installation, it will never do so, when it finds /data/magisk.img.

The installer tells you, what config files it uses, if you can read anything else than 'fallback', you've got a custom .nanomod-setup file at shown path, which may be misconfigured.

* nanomod_forcesystem=1 in .nanomod-setup file, or choosing Foce System Mode from SetupWizard (which the same).

Edit: it says 15:46 for NanoMod install and 15:47 for Magisk, if you want to install NanoMod as Magisk Module, you first have to flash Magisk, then NanoMod. Seems you reversed the order.
[Magisk] AcRs:
Hi, i xannot use any google apps like youtube oor google play games with microg? Thanks
[Magisk] Trademark97:
I am using the setup-wizard, and I am not forcing System mode, so this shouldn't be happening. Attached for help are my recovery.log and my .nanomod-setup file is pasted in (couldn't upload the file proper).

.nanomod-setup contents:

nanomod_microg=1
nanomod_fdroid=1
nanomod_apps=1
nanomod_overlay=1
nanomod_zelda=0
nanomod_mapsv1=1
nanomod_init=1
nanomod_gsync=1
nanomod_swipe=1
nanomod_forcesystem=0
nanomod_sigspoofui=0
nanomod_play=1
[Magisk] Setialpha:
Youtube yes, it's just a html5 video player frontend (basically), Play Games no.

See https://github.com/microg/android_packages_apps_GmsCore/wiki/Implementation-Status
[Magisk] Setialpha:
You saw my edit?
[Magisk] Trademark97:
Sorry, that was me being bad at screenshotting. Magisk was installed first in that instance. I guess if I had had my recovery.log posted than as well that would have been more immediately obvious. I hope that the recovery.log that I did upload should show this situation occurring. My bad.
[Magisk] Trademark97:
Here's another interesting result: installing with Magisk v13.3 causes the proper module-based install to occur, rather than a seemingly automatic System-Mode installation. Also attached is the recovery.log, so that you can compare the two installations and see what occurs differently with Magisk v14.0 .
[Magisk] gimpy1:
Hopefully, you can maybe simplify my reading of this thread? I have last used the nano mod/patcher v.13.1 with Magisk v.13.3.

Now that you have just released v.13.2a and Magisk just released v. 14, are these two releases compatible, or do I stay with the earlier version of Magisk?

Also, in the past, to get my Google calendar and Google contacts syncs working, I have used the Davdroid app and Shadow 53's instructions for syncing them. Is this process still needed, or has that been addressed in the updated nano mod downloads. Note that I only use the nano mod and the patcher downloads. I don't use the set up or the other downloads you've linked.

Thx, for your help and great dev work. Also, thx to all the others who have helped make this system work for all us non techies who don't know what we're doing otherwise.
[Magisk] Ophidian_DarkCore:
New patcher fixed my issue, it works now. good one seti
[Magisk] Anarchy16:
does playstore still have the forceclose issues after succesfully opening it once ?

thx
[Magisk] digitman xxx:
Usually used to install FakeGapps (xposed) to support signature spoofing then install microG project (fakestore.. etc) plus Fdroid

What's the benefits NanoMod offering over these?

Also what should I choose from NanoMod variant if I use MicroG+Fdroid in Lineage13 rom which NOT supporting signature spoofing using SuperSU?
[Magisk] Portgas D. Ace:
As Xposed isn't available for Android Nougat, this mod enables microG to be properly installed on devices with ROM's without signature spoofing, for example.
[Magisk] Setialpha:
The README here on XDA is now the same as the one on github, so you'll now find a lot of icons in the first post, those contains links to project homepages. So if you want to get more information about a specific project or application it's now easy to find that.

Also added a Credits section.

[MENTION=5994172]digitman xxx[/MENTION]

Everything mentioned in first post. tl;dr

No Xposed on Nougat

Modified microG / Play Store to allow (in-)app-purchases

all done systemless

portable patcher (in case of non-pre-patched ROM)

everything mentioned in first post

What variant depends on your need. The full package's setup can be customized (see "Alter Installation"), the f-droid and microG packages only contain given sub-set of the full package. The patcher package contains the on-device framework-patcher.

Read the first post for full information about everything.
[Magisk] facuarmo:
As of v6, Google Play Store keeps giving error 940. Nor rebooting, nor clearing data/cache solved the problem. Switched to OpenGapps Pico until this is fixed.

ROM: crDroid v3.0.

Device: Moto G4 Play (harpia).
[Magisk] Setialpha:
I can't fix it without logcat, as none of my test-devices has this issue (and no one else reported it). Error 940 has a years-long history of suddenly popping up.
[Magisk] toffik325:
Thanks for this module!

Did you consider developing very similar module, but for TouchWiz ROMs? I mean module that would delete any GApps/Google Play/services entirely and replace them with MicroG and YalpStore? I'd love something like this as I'm tired of heavy, not needed services from google draining battery and I didn't find a way to get rid of them on Nougat with TouchWiz :(
[Magisk] Oswald Boelcke:
Thanks to the really powerful and easy to use NanoMod Magisk module by @Setialpha powered by Magisk by @topjohnwu I was able to create a GApps-free system on my Samsung GT-i9305 running Resurrection Remix RR-N-v5.8.3-20170416 by @rodman01. Posting in this section as a different su is involved.

Details to the procedure I used can be retrieved here.

[MENTION=4187311]Setialpha[/MENTION]: Fantastic job! Well done! Thanks very much.:good::good::good:
[Magisk] Kennes95:
Hello guys,

whenever i try to run the NanoMod-patcher i get the following error:

********************************

NanoMod 6.1.20170421

created by [MENTION=7925618]nanol[/MENTION]x

Framework Patcher

Powered by DexPatcher (@lanchon)

********************************

> Android 7.x detected

> preparing environment

Archive: /sdcard/Download/Mods/Magisk/NanoMod/NanoMod-patcher-6.1.20170421.zip

creating: dexpatcher/

inflating: dexpatcher/core_services.jar.dex

inflating: dexpatcher/dexpatcher.dex

inflating: dexpatcher/dexpatcher.jar

inflating: dexpatcher/hook_4.1-6.0_services.jar.dex

inflating: dexpatcher/hook_7.x_services.jar.dex

> patching services.jar

<< this might take a few minutes,

<< depending on your device's power

>> applying hook patch

info: read '/tmp/services.jar'

info: read '/tmp/dexpatcher/hook_7.x_services.jar.dex'

info: write '/tmp/services.jar-hook'

0 error(s), 0 warning(s)

!! zip failed

Updater process ended with ERROR: 1

Can somebody tell me why the patching keeps failing?

Phone: Xiaomi Redmi Note 3 Pro SE (kate)

Rom: AospExtended v4.1

Android: 7.1.2

Magisk: 12.0

Recovery: TWRP 3.1.0-1

Flash order:

Full wipe

AospExtended.v4.1

Magisk-v12.0.

NanoMod-6.1.20170421

Reboot into System

Reboot into Recovery

NanoMod-patcher-6.1.20170421
[Magisk] darhma:
I've the same issue with xiaomi redmi 2 (wt88047)
[Magisk] Setialpha:
See https://github.com/Nanolx/NanoMod/issues/12

I assume your ROMs don't have a zip binary.
[Magisk] SketchyStunts:
Have you tried mounting system in TWRP?
[Magisk] Setialpha:
/system is mounted by my zip. Else it would already fail way before calling zip.
[Magisk] Kennes95:
Unfortunately that didn't solve the problem. But it seems that it took longer before the error message (btw the same as with old version) appeared, so maybe it's failing at another step now.
[Magisk] SketchyStunts:
True.

Just wanted to say this installed & patched without a issue on a LG V20 running EmotionOS 7.1.2

Thanks a bunch for this.
[Magisk] Oswald Boelcke:
I used a slightly different flashing/reboot sequence. Please find details here.

Maybe that sequence is going to work for both of you. Hopefully...
[Magisk] darhma:
I think the problem is this with AOSP Extended 4.1 because I tried with Resurrection Remix 5.8.3 and all goes well.
[Magisk] droika:
On my LineageOS 14.1 ROM "system" does not "support location services", also the "GSM based location service" is disabled. Any way to fix that?
[Magisk] Setialpha:
For everyone having issues with the on-device framework-patcher failing upon zip, check out this post I made in the github repository for test flashable zips, which both should work, please report your results for

both

zips here (or over at github).

Thanks.

========

Did you setup microG like described in first post? Is your ROM GApps-free?

If both is the case (and you've rebooted at least once) please provide a logcat.
[Magisk] droika:
Thanks for your fast reply!

I did, yeah. And it's GApps-free.

Here's my log:
[Magisk] rignfool:
I have a question for you trailblazers....

Does running this mod curb the NLP check-ins?

When using Google services... Your device wakes up once a minute for a few seconds to let the mothership know your network location...

Can the same be said for going this route? Or is it controllable? Or is it just less...

I'm bored... And I need something new to play with... Like this mod... But my primary goal is always better battery life...
[Magisk] Setialpha:
Ehm, the 13.2a Changelog has only one enty:"fix bootloop with Magisk 13.5 / 13.6 / 14.0"

NanoMod includes Sync Adapters in separate versions for K, L, M, N and O, just enable them within setupwizard.

I never had that kind of issue and afaik no one else ever reported it, so it's either a very specific corner case or fixed.
[Magisk] Shadow53:
I don't use Google's sync adapters since I have my own DAV server I use, but iirc [MENTION=4187311]Setialpha[/MENTION] based his sync add-on off of my own, so it should work. You may need to manually grant permissions to the sync adapters and/or manually start a sync for it to work, though.

TL;DR: If you're not using Google's Play Services, maybe you shouldn't use Google for contact and calendar sync :p
[Magisk] Anarchy16:
i just flash it but has to revert back, issues still happen in my end.

clean flash > vertexos 3.5 (op3) > latest nanomod MicroG (system) > magisk 14 > reboot > setup everything > reboot

login, my account registered & contact sync successfully .

open playstore for first time its open and prompt me this (screenshot)(accept). and after i close playstore, and reopen it, thats where playstore crashes !

when i clear data for PS, its open again and prompt again, but if i close PS and reopen, force close again . weird huh :confused: ?
[Magisk] Setialpha:
logcat?
[Magisk] Anarchy16:
im sory, forgot to log, i now revert to my os

will do it later
[Magisk] Anarchy16:
here log, i hope this log is correct
[Magisk] Setialpha:
Thanks, will have a look after work.
[Magisk] dorian5752:
@ Anarchy16:D

for the playstore that opens after opening it, download a file manager, navigate to system / priv app then go to phonesky apk and click on install erase the data from the play store before restart your terminal for me its a rsolu the crash problem
[Magisk] demonoidmaster:
Edit nvm
[Magisk] Trademark97:
Any good news on problem? I eagerly await your response, and thank you very much for continuing to help and to provide this wonderful tool.
[Magisk] ShapeShifter499:
I don't know what's up but the 13.2a patcher seems to be patching the system.apk wrong for "Signature Spoofing toggle in Developer Settings" for Nougat 7.1 LineageOS 14.1 It's crashing on me and I can't get a log right now.
[Magisk] Setialpha:
There sould be a backup of the unpatched file at /sdcard/Settings.apk as a quick fix. But signature spoofing then won't work, as the toggle is inactive by default.

I tested it and it worked here, dunno if LAOS changed anything, if so, the haystack patch needs to be updated.
[Magisk] Reylom:
Hi

Yes, here.

Second :D

After "complete" update (Redmi Note 4X; TWRP 3.1.1.0) yesterday: Lineageos update to 7.9., magisk 14 and NanoMod-microG-13.2a.20170906 (all flashed via TWRP: ROM > Magisk > NanoMod) all looks fine until the playstore. He crashed after first successfully opening. And also if i open some apps (like file explorer (x-plore))

I will try this later:

and

Another question:

How can i do this? Via App (SD Maid maybe?)

View attachment 4266521

Correct?
[Magisk] Oswald Boelcke:
Negative, not by SD Maid (it only allows to enable/disable broadcast receiver) but with MyAndroidTools or Elixir2.

No FCs of Play Store at all; however, I reverted back to Magisk v13.3 from v14.0 after less than 12 hours (didn't check the Play Store during this time frame) as I got an unintended reboot. With v13.3, I haven't had any reboots and still don't have.

EDIT: Added screenshot of the services I've disabled in Google Play Store without any restrictions to functionality.
[Magisk] ShapeShifter499:
I redid the patching, the settings.apk works fine if you only run the signature spoof patch. The problem seems to be with the extra "GUI toggle" patch, I can live with signature spoofing on all the time. Why would you need or want the toggle in developer settings anyways, is there a good reason to turn off signature spoofing sometimes?
[Magisk] Setialpha:
Settings.apk.

The toggle is optional, as I don't see why you'd need it, but it's there, so it is supported.
[Magisk] Oswald Boelcke:
New GmsCore

microG Project has release a new preview release of Services Core ("com.google.android.gms") version 0.2.4-105-gf289a13.