yashsingh1/xdaforums huggingface dataset:
[Magisk] sudokamikaze:
I think, opengapps rewrites it to newer version and it magically works
[Magisk] Reylom:
Hi
[MENTION=4187311]Setialpha[/MENTION]

I've a Samsung Tab S2 (T710) currently with the Poseidon ROM, up to date TWRP & Magisk. After i have manuelly removed (almost) all google-packages (according to this guide) i have installed NanoMod-microG. That's fine, but if i try to flash the NanoMod-patcher via TWRP after some time the process ends with an error: "Prozess Updater endete mit FEHLER: 1"

The note "post your /tmp/recovery.log" i have read, but in which directory i can find this log in order to post it here in the thread?
[Magisk] Oswald Boelcke:
On my device, the recovery.log is copied to extSD. If you select in TWRP "copy log", TWRP (mine v3.0.2-1) tells you where it was written to.

Did you once reboot after flashing of Nanomod-microG and before flashing of the patcher?
[Magisk] Setialpha:
Just as it says: in /tmp. You can use TWRP Advanced > Copy Log to SD, you'll then find it in /sdcard.
[Magisk] Setialpha:
I made a change, so that vendor libraries are included in LD_LIBRARY_PATH. Please try again, it should now find -lsecpkcs11_engine.
[Magisk] Reylom:
Looks great. Quickly tested and the patcher runs both processes :good: In the microg settings also everything is green :D

Now i can reinstall the Rom from scratch and test it extensively.

Thank you for your (late) work
[Magisk] demonoidmaster:
I noticed the lines

*remove empty directories

*/system/app

*/system/priv-app

Hopefully it doesn't force wipe those folder even when they've got files in em
[Magisk] Setialpha:
Nope, don't worry, it's well tested, also 'rmdir' is technically not capable of removing directories with content.

Also only applies for System Mode.
[Magisk] hungvip2001:
New version works like a champ. All items of microG SEFT-CHECK are checked which the previous version can't be. Thank you so much dev. Keep working
[Magisk] kurtn:
Hi Setialpha, thank you for that hard work. I've been using the first patcher with .nanomod flag file up till now. Works without any problem on LineageOS each week. - one time my TWRP script did not start, but I think that is not your fault.

Doday I updated to 13.0. Sadly I can't find the toggle.
[Magisk] Setialpha:
Did you set

nanomod_sigspoofui=1

in your

.nanomod-setup

file? Or - if you use the Setup Wizard - did you tick that option?

It's

not

enabled by default.
[Magisk] super-drone:
Hello guys, so I'm new here, and I wanted to know if I can update this module just flashing zip on twrp or should I do a clean flash? I'm on 12.1 version, thanks in advance, great job!
[Magisk] demonoidmaster:
Flash Magisk 13.3 (go to the magisk main thread) if you haven't yet

As for this, if you already had this module installed and stuff then yeah just flash the update zip in twrp
[Magisk] super-drone:
I already have the module installed in this case, thanks for the help
[Magisk] psychoela:
using magisk 13.6 beta:( thanks
[Magisk] pinoholo:
Clearly OP state to stick with stable magisk 13.3

Try 13.3
[Magisk] kurtn:
I didn't have a setup file up till now. Now I have the toggle. The alert text sounds like there is an extra permission to grant. Instead I had to reboot after toggling.

Reflashing ROM (dirty) an patcher doesn't alter toggle setting.
[Magisk] Setialpha:
The Toggle itself is the master switch to enable ir disable the permission.
[Magisk] evilvoice:
Okay, I see a lot of work went into separating the sync files by OS, but I have an issue with the lollipop version. The one included is for 5.1.1 and API 22. I'm on 5.0.1 and API 21 so the contact sync adapter isn't working, nor the backup transport.
[Magisk] Setialpha:
I'm shamlessly using the Sync Adapters provided by [MENTION=7126506]Shadow53[/MENTION], so the issue also exists for people using his website.

I've re-uploaded the F-Droid package to fix the bug in the installer.
[Magisk] evilvoice:
Currently, to fix the issue, I'm pulling the contacts sync from open gapps and replacing the file. Just wanted to let you know about it. I think someone else said they were flashing open gapps and that it was fixing an issue, so that could be it.
[Magisk] puhu:
Sorry Im really noob on this topic and i read the first page again and again but what is that module? What is for it? Should i install this pls help me!

MI 5 cihazımdan Tapatalk kullanılarak gönderildi
[Magisk] marcdw:
Short answer: No.

To be honest, if you don't know what it is or what it is for, even after reading about it multiple times, then you have already answered your question.

There is no reason to ask us if you should install something or not. Only you would know. Determination based on a want or need.

Start off by learning about microG. Its purpose, benefits, limitations, etc. Can you live without a bunch of Google apps?

Check out the microG thread for more information.

http://xdaforums.com/showthread.php?t=3217616

[APP] microG GmsCore - lightweight free software clone of Google Play Services

LG G3 D851, LiquidSmooth v4.1 ROM, MultiROM, Tapatalk 4.9.5
[Magisk] kurtn:
[MENTION=6046143]marcdw[/MENTION] gave you the technical background. For the question WHY there is more ideological background in https://shadow53.com/android/no-gapps/faq/why-should-i-care/
[Magisk] Shadow53:
And I'm shamelessly using your patched Play Store ^_^

Anyways, about the issue: I made the assumption that people still on Lollipop would be using the last version. I just got to work for the day but I'll put adding 5.0 on my list of things to take care of after work.
[Magisk] Anarchy16:
known issues ? droidguard FC when checking safetynet

latest stable (as module)

magisk v13.3

rom : aex 4.5 (op3)
[Magisk] super-drone:
Yes, its on second post
[Magisk] evilvoice:
LOL. Well you know what assuming does j/k. I would be on the latest version of LP if it ever came out for my phone (stock, that is). Unfortunately, Samsung decided to never update the Note 3 past 5.0.1. Really thought it would be upgraded to at least 5.1.1 or 6.0, but nope.

It's only the contact sync adapter and backup transport. I pulled from the latest 5.0 open gapps aroma and pushed to system. Finally I have contacts syncing. The calendar sync is fine.

Side note to anybody: is there a reason to have calendar sync for microg? I removed the calendar, so it's not like it's syncing. Just wondering if there is maybe something embedded in android that uses it besides the calendar app. Thanks

And thank you [MENTION=7126506]Shadow53[/MENTION]
[Magisk] Setialpha:
May I say, that I'm currently running an updated patcher on-device *without* dalvik-cache in place? Read: without booting into the ROM once?

1st patch takes as long as with current patcher, 2nd patch is faster applied (if sigspoofui is patched, 3rd and 4th, aswell).

Need to check if I can speed up things, no ETA yet, but beta build for patcher comes soon™.
[Magisk] Shadow53:
Do you have plans to make the patcher automatically patch the system on a system update, i.e. with addon.d? I know the Magisk patcher is capable of that, but not sure how it does.
[Magisk] Setialpha:
Haven't thought about that, yet, but would certainly be useful no?

The Magisk Module simply keeps the patched file, as long as /system/.nanomod-patcher exists. During module update it gets copied to TMPDIR and then reinstalled.
[Magisk] Shadow53:
I think you misunderstood. By the Magisk patcher, I meant the part of the Magisk (not NanoMod) installer that patches the boot image for root. When the system updates over OTA, it automatically patches the new boot image for you.
[Magisk] Setialpha:
Ah, OK, yes, I misunderstood.
[Magisk] CHEF-KOCH:
It seems there still problems with the patcher (I not want to complain but just help cause people might getting error:1), because when you're upgrade your LineageOS and you patched it before you might receive error:1, when this happens you can or need to clear the davlik/arm cache till the old 'crap' was removed, sometimes it takes 2 or more times. So I think this must be fixed in the future patcher builds. I'll attach a log as soon I flash another nightly and let you know what it says. I'll edit this post here.

There only minor changes which needs to be done, also wanted to say that over the past months/weeks there was a great process in this project here - so a huge thanks from me to continue the work here!
[Magisk] Setialpha:
Since the

shiny new

patcher will create it's own, temporary, dalvik-cache that problem should no longer appear. Stay tuned, gonna upload very soon(tm).
[Magisk] Setialpha:
Patcher 13.1-beta1 (Next Generation)

So, as promised a few hours ago. There's the first build of the next generation NanoMod-patcher.

So, what has changed since 13.0:

update `dexpatcher` to 1.3.0

remove unused dexpatcher.jar file

run `dexpatcher` using up to 4 CPU cores (if available)

no longer requires booting into ROM before patching

more reliably catch `dexpatcher` errors

do all `dexpatcher` operations in `BASEDIR`, not `TMPDIR`

clean-up environment (ensures patching more than once per session creates proper result)

Yes, you've read right, no longer booting into ROM. This new build of the patcher creates it's own, temporary dalvik-cache, thus it's independent of the state of the ROM.

My test results:

Device: Samsung Galaxy Tab 4
- wiped /cache and dalvik-cache
- time to create private dalvik-cache: <1 Minute
- time to patch core/hook base patches: ~1 Minute
- time to patch ui extra patches: <2 Minutes

So enough blabla, grab the attached zip and let me know whether it works for you.

Ah, currently only tested flashing using TWRP, but should work using Magisk Manager aswell (as nothing in this regard changed).
[Magisk] CHEF-KOCH:
Awesome dude, you never sleep it seems! I'll test it and report back, For sure, only need to wait till next nightly. :D
[Magisk] demonoidmaster:
You asked if installing newer zips onto of your current one is ok, i told you it is

I didn't ask if you already had the module installed
[Magisk] Trademark97:
So far, this is working swimmingly on my device. As you already know from our other endeavor (getting the resize functions to work), I use a Moto G4 (XT1625 model). I decided to try a ROM that doesn't natively have SS support (ResurrectionRemix) and did the following procedure:

1. Push all relevant files to device

1a. RR-5.8.4 (latest ZIP)

1b. NanoMod v13.0 full ZIP

1c. NanoMod v13.0 setupwizard ZIP

1d. NanoMod v13.1-ng-b1 patcher ZIP that you just put out

2. Flash RR v5.8.4

3. Run NanoMod setupwizard

4. Flash NanoMod full zip

5. Run patcher

6. Reboot

I haven't done a lot with the setup yet, but so far everything I have tested is running just fine and dandy. Unfortunately, I won't be able to test to see if the patcher can persevere across dirty flashes (as I always heed the advice of the ROM maintainers and flash clean). But so far, I can see nothing wrong, and I am successfully using one of my all-time favorite ROMs, with NanoMod, to great effect. Thank you very much, kind sir, for continuing to provide this wonderful project that puts so much extra speed and battery life into my device.
[Magisk] disposaber:
After installing the module (version 13 using TWRP) systemless-ly, my phone doesn't turn off. The screen turn off but the buttons bright. It's a redmi note 3 pro (kenzo). The project is wonderful and works like a charm except for that. Thank you very much.
[Magisk] kurtn:
No luck with clean lineage+addonsu+patcer
[Magisk] Setialpha:
No detailed information provided, please provide a recovery.log.
[Magisk] kurtn:
And no luck with uploading log file
[Magisk] kurtn:
And no luck with uploading log
[Magisk] Setialpha:
Sorry, I haven't checked the post properly, just saw no log, so I overdid it.

I've found the issue and will provide a fixed build later today.
[Magisk] piet8stevens:
Impact of system partition file system change on Nanomod/Magisk?

I switched my kernel to Radioactive and phone worked well without reinstallation of Magisk/Nanomod.

Then I changed my system partition file system to f2fs, reinstalled the same rom (RR 0811 version) after wiping dalvik/cache (so dirty flash), reinstalled magisk 13.3 and nanomod 12.0. Rebooted + then did nanomod-patcher 12.0. Very strange effect: Magisk manager sees no internet connection but applications I installed myself do have wifi. For example, lightning browser gives no internet connection error but brave browser has no problem. Magisk manager also indicates no internet when doing Safetynet check.

Any ideas?
[Magisk] CHEF-KOCH:
Yep, reinstall the apps and check their permissions normally no internet is a permission problem.
[Magisk] Setialpha:
First of all I suggest using NanoMod 13.0, as it fixes

many

bugs.

If anything it is more an issue with Magisk, since NanoMod does only provide apps, scripts, tools and libraries. I suggest providing a logcat, else I can just make guesses.
[Magisk] gimpy1:
To get the Magisk internet working, I always have to install the droid guard helper apk. I always have to do that on a new install.
[Magisk] Setialpha:
Patcher 13.1-beta2

A new beta version of the new Patcher is available. Changes since beta1:

prevent dalvikvm from creating a useless log message

use grep instead of nproc for aquiring no. of available cpu cores (higher compatibility)

re-check for /system/.nanomod-patcher

[MENTION=8031265]kurtn[/MENTION] #2 should fix the issue you're having.

For what's new at all with the "next generation" of the patcher, refer to beta1 post.

Download the attached file and report back any issues.
[Magisk] kurtn:
Fixed. Side-effect: [MENTION=7126506]Shadow53[/MENTION] 's microg-playstore now has most permissions. Without needing to grant one by one.
[Magisk] kurtn:
Tried [MENTION=4544860]osm0sis[/MENTION] ' flashafterupdate script. Patcher stopped with error code 1. How can I get recovery.log after automatic system restart?
[Magisk] Setialpha:
You can't, it gets deleted. Never tried flasafterupdate, is it possible to prevent restart, or save the logs?
[Magisk] demonoidmaster:
Js but no point in making system f2fs because if you flash RR it formats your system partition as ext4 to work sooo yh js lol

Having data and cache be f2fs is no issue, works with ext4 system partition
[Magisk] kurtn:
When I start the update in TWRP the flashafterupdate gest started as well, but no restart. Here is the log.
[Magisk] Setialpha:
Try this build if it works.
[Magisk] kurtn:
Does not
[Magisk] Setialpha:
My ROM does not execute FAU at all... but running the FAU script manually works for me as it should. Any advice [MENTION=4544860]osm0sis[/MENTION] ?
[Magisk] piet8stevens:
Thank you, you are quite right and I had not noticed before: RR reformats system partition as ext4. Hmm, will have to start looking for a ROM that does not do so on my Axon7.
[Magisk] kurtn:
How did you run FAU?
[Magisk] osm0sis:
Does your ROM not have addon.d or something?
[Magisk] Setialpha:
It does, but it's broken. It's a Feb build of crDroid for Galaxy Tab 4, not much love for this device. Hadn't had the chance to test on a different device yet.

I manually called

99-fau.sh post-restore

which creates ugly output to stdout, but works. Though it seems not to work through addon.d, unzip complains and then segfaults follow, see [MENTION=8031265]kurtn[/MENTION] logcat.

Unzip fails in 99-fau.sh, but I don't know where the segfaults come from...
[Magisk] piet8stevens:
Beta2 works for me - Nanomod install + patching without rebooting into ROM. Thank you. OS RR, phone Axon 7, Magisk 13.3, Nanomod 13.0, Radioactive Kernel.
[Magisk] osm0sis:
Well you're making it run booted and it's meant for TWRP's environment during a ROM's addon.d.. you should complain to your ROM dev and have them fix addon.d, no?
[Magisk] Setialpha:
Well, I called it from TWRP. Either way, will see what I can do...
[Magisk] :
My TWRP 3.0.2 stopped at "GNU Bash, Nanomod-Overlay" and nothing changed for about 10 minutes :/ (LG G3 D855 android 6.0, Magisk 13.3).
[Magisk] demonoidmaster:
Update TWRP lol

https://dl.twrp.me/d855/
[Magisk] Wyroczen:
With 3.1.1 the same
[Magisk] demonoidmaster:
I know, i only wanted to tell ya to update twrp cuz you're using an old version
[Magisk] kurtn:
Besides [MENTION=4187311]Setialpha[/MENTION] 's addon.d, what's your opinion about the nanomod-patcher? It works when started manually, but not in flashafterupdate mode.
[Magisk] kurtn:
Running magisk 13? Try Magisk 12: https://xdaforums.com/showpost.php?p=72855458&postcount=2217
[Magisk] Pierroxx:
Hey !

This is a great module, microG with patcher is running great on my xiaomi Mi 5S with Viper OS (nougat) !

But, on sync option with google account, i only got news&weather and inbox. There is no contact sync and everything else. (The only thing i miss is contact sync btw).

I am using aosp contact app, i could add some account on contact app, but nothing happens when pressing it.

Did i miss something in app config ?

Thank you for your work and support.
[Magisk] slothdabski:
Custom build of Resurrection Remix N with sultanxda optimizations, camera, and kernel. I used the nanomod patch to be able to use signature spoofing on it.

Here's the link to the ROM, kernel is included

https://androidfilehost.com/?fid=529152257862719563
[Magisk] aldanopolis:
Im using the latest version of this module, and when I try to install some apps I get error -507, anybody knows how I can fix it? Sorry for the English

Enviado desde mi Moto G mediante Tapatalk
[Magisk] anunaym14:
I am on OnePlus X. Can u pls guide me through the steps of using signature spoofing with nanomod patcher...note that i have windows (adb is working fine), also tell if i need to download something else also..thx in advance
[Magisk] CooperBrick:
There are some apps that don't work without play services... Is there a way to bypass this thing or do we have to use other apps?
[Magisk] candiesdoodle:
install this

https://github.com/microg/android_frameworks_mapsv1/releases

or use "nanomod.mapsv1=1" in /data/.nanomod-setup [though i suspect this may not work if you have already installed; use the first method -

should work; else check in logcat why is the app not getting installed]

---------- Post added at 02:23 PM ---------- Previous post was at 02:22 PM ----------

@slothdabski .. superb module. just what was needed

quick question - what is the easiest way to uninstall the FOSS apps once already installed? since they are pseudo mounted to system
[Magisk] anunaym14:
Error [RH-01]

I spoofed via tingle. Flash Nanomod (MicroG variant), I couldn't find any microg settings icon in launcher drawer. I went to settings-->apps-->then gave all permissions to MicroG.

Then when i open play store, it says Error retrieving information from server.[RH-01]

What can be done?

Please help me!

Edit: Sorry, extremely sorry, there is microg settings icon, i mis-interpreted it as normal settings!
[Magisk] slothdabski:
Use the microg zip if you only want microg and nothing additional. Or edit the file mentioned about using info from OP to select what does and doesn't get mounted by editing /data/.nanomod-setup file

---------- Post added at 05:57 AM ---------- Previous post was at 05:54 AM ----------

At that point all you need to do is reboot, as mentioned in OP. Then play store should connect. If any Google apps don't see your play account, make your you go to settings and manually grant permission for contacts for that app
[Magisk] Setialpha:
Accidently quoted wrong post
[Magisk] Setialpha:
A) 'nanomod.mapsv1=1' is new in 5.3, current pre-built 5.2 zips don't have this feature. But flashing 5.3 with that setting over 5.2 would of course work.

B) Remove them from '/magisk/NanoMod/system/app' and reboot. Or use 'nanomod.apps=0'.
[Magisk] Setialpha:
6.0 now available

Version 6.0 released.

Biggest new features:

the .nanomod-setup and .nanomod-overlay file are now stored directly in /data, thus they can now be properly accessed when using adoptable storage

on-device framework-patcher for microG fake signature spoofing support (read the Installation paragraph carefuly for notes on this) available as flashable zip

the microG package now also supports the pseudo-debloat feature (but unlike the full package you need to manually set it up, the README has all required information readily available)

f-droid only package available

Full ChangeLog since 5.2:

* Internal Changes
* there's now an F-Droid only variant
* there's now an on-device framework-patcher
* Note 1) after **full wipe** it is suggested to boot into the ROM once, else the dalvik-cache does not exist and the patching process takes ages
* Note 2) pro tip: if your ROM supports automatic OTA udpates with the ability to flash extra zip file, place the `Magisk` and `NanoMod` zip files in that directory which holds that extra auto-flashed zip files, so the OTA updater does all the work in one go
* ensure all binaries installed by NanoMod (full package) are executable
* minor fix in `nanomod-overlay` script
* added `fdroid` parameter to `mod.sh`, to create the F-Droid only package from git
* added `patcher` parameter to `mod.sh`, to create the on-device framework-patcher package from git
* revised `mod.sh` (cleaner code)
* revised `mod.sh` (should now be fully functional on Mac OSX)
* added `nanomod.mapsv1` setup variable to `nanomod-setup` configuration file
* the location of the `.nanomod-setup` file was changed from `/data/media/0/.nanomod-setup` to `/data/.nanomod-setup`
* if the old file is found, the installer will move it to the new location
* this is in order to ensure the file is usable when users have adoptable storage in use
* the location of the `.nanomod-overlay` file was changed from `/data/media/0/.nanomod-overlay` to `/data/.nanomod-overlay`
* if the old file is found, the installer will move it to the new location
* this is in order to ensure the file is usable when users have adoptable storage in use
* also install the `nanomod-overlay` script in the microG only package
* so that `nanomod-overlay -p` is available
* revised README in many places
* README now features many graphical links for most things featured in full package, pointing to F-Droid pages, github repos, or the-like, to make it much easier to get additional information
* Updates
* F-Droid (0.103.alpha2)
* AnySoftKeyboard (1.8.735)
* NewPipe (0.9.2)
* Play Store (7.7.17.O)
* Amaze (3.1.2~beta10)
* Substratum (671)
* Twidere (3.5.18)
* K9-Mail (5.207)
* (Simple) Gallery (2.8.4)

On a side-note: the on-device framework-patcher supports the following installation paths for the patched services.jar:

NanoMod Magisk Module (full)

NanoMod Magisk Module (microG)

ROM (directly into /system/framework

So even if you don't use NanoMod, you can use it's patcher to make your ROM microG-ready.
[Magisk] candiesdoodle:
Awesome stuff. Going to try v6.

Quick question - is there ant way to get Google now feeds to work? I know it's stupid to expect, but all other Google apps work fine. So if anyone knows how to get it to run, that will be great!
[Magisk] Setialpha:
I never tried that, you can collect a logcat, if it complains about a missing function, you may open a feature request in the microg github repo.
[Magisk] atendedor_de_boludos:
Request:

Option to choose which apps can be installed in nanomod.apps

These apps are installed by user app (can be uninstalled) or pseudo-system?

Maybe a noob question, just for clarifying, If I will patch the framework for signature signing manually (not your framework-patcher.sh) with the Haystack's way, I will able to pass Safetynet or your both methods (zip and script) are the only ways to pass?

While type this the answer seems obviously but anyways...

correct this

nanomod.play=[0|1]

whether to populate Zelda ringtones and sounds.

Also I want to say thank you for this awesome mod

Sorry for my bad English
[Magisk] rohit83:
Guys, facing major problem here on my bqcon crdroid rom, i tries with mozilla it doesn't show my exact location, even tried with gsmnlp locator still it shows location 3 kms away from original in maps. Pls help asap
[Magisk] slothdabski:
I can pass safetynet after using on-device framework patcher