yashsingh1/xdaforums huggingface dataset:
[Magisk] demonoidmaster:
Yknow, stuff like substratum and such playstore apps, i don't get why you bundle them with these since anyone using the playstore or yalp (amazing app though omg *note v19 of yalp is broken, v18 works fine so stick with that Seti, don't bundle v19*) could download them + they'd get updated whenever there's an update on the playstore
[Magisk] droiduin:
Hi,

Would you be willing to share it?

Thanks
[Magisk] Setialpha:
Well, I'm not looking forward to discuss this actually, but: NanoMod started out as a personal project. I wanted a flashable zip that does everything I want, regardless of the ROM used, regardless of underlying device, without further steps, OTA safe, systemless.

While the whole thing evolved further, separate microG and F-Droid packages where created, since I know, not everyone's me.

Further down the road I incorporated a lot of feedback and requests from users, targeting the new in 12.0 Setup Wizard to give users full control at the end.

Yalp Store is bundled in version 0.21.
[Magisk] kurtn:
Rename the patcher to emulated/0/fau.zip
[Magisk] meistr91:
Hello. Want to thank you for mod, really helpful and making it easier for setup microG. I got safety net passed, google sync, everything seems working properly, but i cant create any folder in /system. Actually it creates folder i can paste apk everything going good until i reboot device. After reboot folder and apk is gone. It should be something from this mod couse im using same setup just + nanomod. And without this mod i can copy files into system.
[Magisk] droiduin:
Interesting. Searching the web I couldn't find any reference to this mechanism. How does it work and what's that flo binary in the attached zip doing? Would you mind publishing its source code?

Looking at the binary it seems like it might check whether /system/.nanomod-patcher exists (system already patched) and if not reinstalls the patcher via a TWRP OpenRecoveryScript (as /cache/recovery/openrecoveryscript) that runs "install data/fau.zip" (hence the need to copy the patcher to /emulated/0/fau.zip first). When is that script actually triggered?

Ah, as you said earlier, it's an Automate flow, duh! Thanks, I'll look into it.

Cheers
[Magisk] hungvip2001:
Flashed micrG nanomod v11, v12 and v12.1. Everything work but after few hours, microG app 's setting auto reset and I have to set it manually again. Any idea ?
[Magisk] 1plus:
in the latest Nanomod, Orfox never works but force closes. Any kind of permission problem? LOS 14.1.

08-08 09:54:56.029 I/GeckoApplication(11275): zerdatime 29942635 - Fennec application start
08-08 09:54:56.061 D/GeckoApp(11275): Enabling Android StrictMode
08-08 09:54:56.069 I/GeckoThread(11275): preparing to run Gecko
08-08 09:54:56.073 D/GeckoSharedPrefs(11275): Current version = 2, prefs version = 2
08-08 09:54:56.079 D/GeckoScreenOrientation(11275): updating to new orientation PORTRAIT_PRIMARY
08-08 09:54:56.081 E/linker (11275): readlink("/proc/self/fd/33") failed: No such file or directory [fd=33]
08-08 09:54:56.082 E/linker (11275): warning: unable to get realpath for the library "/system/app/Orfox/lib/arm/libmozglue.so". Will use given path.
08-08 09:54:56.101 D/GeckoLoader(11275): Gecko environment env0: null
08-08 09:54:56.128 E/GeckoLibLoad(11275): Load sqlite start
08-08 09:54:56.137 F/libc (11275): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 11292 (Gecko)
08-08 09:54:56.138 W/ (3206): debuggerd: handling request: pid=11275 uid=10102 gid=10102 tid=11292
08-08 09:54:56.187 F/libc (11275): failed to resend signal during crash: Operation not permitted

btw there are plenty of "unable to get realpath for the library" warning messages in the log, I guess that's because of Magisk?
[Magisk] demonoidmaster:
Ahh i see

And for Yalp, in v19 the apps list of updates would magically disappear even if there's updates (a bug) so i wonder if it's fixed in v20 and v21
[Magisk] Blackcrown:
Yes, Yalp works fine in v20. Dunno about v21, because I updated only recently.

Gesendet von meinem KFDOWI mit Tapatalk
[Magisk] demonoidmaster:
Guess they've fixed the bug then
[Magisk] Setialpha:
Likely a bug in Orfox 1.4-RC2, you can update to RC3 using Play Store or Yalp Store. Or download manually: https://guardianproject.info/releases/Orfox-v1.4-RC-3.apk
[Magisk] Setialpha:
Nipe, never heard of that, but I'd need a logcat to have a look at.
[Magisk] meistr91:
If we talking about same thing, so its still presist on yalp v21 . Everytime i open yelp i have blank screen no apps listed i need press refresh button, but i for me its not big deal
[Magisk] Max Line:
Cant install nanomod microg

Magisk is crashing and i'm getting the following error:

"<< installing microG

dir: /dev/tmp/NanoModmicroG/system/app/nlpBackendIchnaea

!! installing libs for nlpBackendIchnaea.apk failed

Failed!

"

What could be the issue and how can I fix this?

Im running the lastest version of resurrection remix on a oneplus3T.
[Magisk] Setialpha:
Flashed through TWRP or Magisk Manager? If the latter, flash from TWRP instead. What version?
[Magisk] Max Line:
I flashed it through magisk.

When I tried flashing from twrp, it was ok. When flashing the patcher through twrp I got error 1.
[Magisk] Setialpha:
Need full recovery.log for patcher, patch failing can have various reasons.
[Magisk] Max Line:
Didn't flash the patcher this time, only flashed the old one over the new microg and it seems to work. So that's a possible solution for now.
[Magisk] Ophidian_DarkCore:
if you have patching issues check out tingle. it works for me, seeing how the patcher hasnt function for a long time on my gs5
[Magisk] Setialpha:
While the installation instructions state to flash through TWRP and not Magisk Manager, people still do...

So, that's just a quick heads-up that version 12.2 will be

first-in-ages*

that properly installs trough Magisk Manager. ChangeLog for those changes:

* Bug fixes
* Full, microG, F-Droid, Framework-Patcher packages:
* use `/dev/tmp` instead of `/tmp`, fixes several bugs when installing from Magisk Manager
* Full, microG packages:
* fix back-up and restore of `services.jar` when installing from Magisk Manager
* fix `nanomod_substitute` not creating expected result when installing from Magisk Manager
* fix pseudo-debloat feature not enabled when installing from Magisk Manager

Flashing the Framework-Patcher through Magisk is still untested, but

may

eventually work, aswell.

If you wanna test, you can create a new package from the git repository, no new beta (yet).

* Yes, you've read right: previous versions did not properly install through Magisk Manager.
[Magisk] justbfree:
Error while flashing nanomod fdroid

Hi, I'm getting error while flashing latest version of nanomod fdroid in twrp.

But when I while the previous version it works.
[Magisk] marcdw:
Could be a bad zip. Redownload and try again. Otherwise, provide a recovery.log.

ZTE Axon 7 A2017U, Dark ROM, Tapatalk 4.9.3
[Magisk] ShapeShifter499:
[MENTION=4187311]Setialpha[/MENTION] My device started crashing, none of the NanoMod installed apps would open resulting in a lot of "<app> has stopped" popup messages, even OpenLauncher will not load. This was after I updated to the latest LineageOS nightly, 08/07/17 and then flashed the newest NanoMod in TWRP (NanoMod-12.1.20170807). Here is a Logcat I took, https://gist.github.com/ShapeShifter499/5c35d4e4211828ff02a0691c21270297 has a bunch of odd crash messages that I'm not 100% sure what to make of.
[Magisk] Setialpha:
I'll have a look, from a quick check there seems to be issues related to permissions, but nothing changed in this regard in NanoMod. What version of Lineage did you use before (so I can check the ChangeLog)?

You may try clearing cache/dalvik-cache and see if it changes anything. Last instance would be to do a TWRP backup and check what happens in a clean flash, if it works with a clean flash, then something gone wrong during the update. That's something I experienced pretty often with various packages during the times I still used nightlies.
[Magisk] Setialpha:
13.0-beta1

Version 13.0-beta1 is now available. Highlights since 12.1:

Full, microG and F-Droid packages are now correctly flashable through Magisk Manager

Patcher package is now flashable through Magisk Manager (not much tested yet)

Patcher package now honours nanomod_forcesystem setup variable

separate GSync Adapters for LL, MM and N

Feel free to test and report any occurring issues.

Full ChangeLog since 12.1:

* Bug fixes
* Full, microG, F-Droid, Framework-Patcher packages:
* use `/dev/tmp` instead of `/tmp`, fixes several bugs when installing from Magisk Manager
* Full, microG packages:
* fix back-up and restore of `services.jar` when installing from Magisk Manager
* fix `nanomod_substitute` not creating expected result when installing from Magisk Manager
* fix pseudo-debloat feature not enabled when installing from Magisk Manager
* Full, microG packages, Framework-Patcher packages:
* fix `/system/.nanomod-patcher` handling when installing from Magisk Manager
* Framework-Patcher package:
* properly install `services.jar` into merge-pending NanoMod Magisk Modules
* don't mount `/system` twice and don't try to unmount it, when installing through Magisk Manager
* General Changes:
* Full, microG, F-Droid packages:
* ignore `nanomod_forcesystem` when installing through Magisk Manager
* deeper indent `nanomod_libs` output, makes recovery.log easier to read
* Full, microG packages:
* update swipe libraries for x86_64
* provide separate Google Sync Adapters for LL, MM and N, install correct version
* first print messages then do installation of the given component, not the over way round
* makes it easier to understand the recovery.log
* Framework-Patcher package:
* check for `.nanomod-setup` and respect `nanomod_forcesystem` property
* Documentation:
* add various additional links
* other minor improvements
* build-package:
* `swipe` parameter updates swipe libraries using shadow53's website
* `gsync` parameter updates gsync apks using shadow53's website
* Updates
* Orfox (1.4-RC3)
* Simple Gallery (2.13.0)
* Twidere (3.6.24)
* Yalp Store (0.22)
* Play Store (8.1.29.S)

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] ShapeShifter499:
Last working LineageOS nightly for me was "07/31/2017" for Moto X Pure (clark).
[Magisk] CHEF-KOCH:
V13 beta 1 Patcher error 1

https://pastebin.com/d5QRvZHi

Log fixed
[Magisk] Setialpha:
That log does not contain any flashing info. Need a log after flashing.

Edit: OK, I see, will update, soon.
[Magisk] Setialpha:
13.0-beta2

Second beta for v13, with the following fixes since beta1:

fixup nanomod-overlay when no config exists (in-ROM)

Patcher: fix TMPDIR issue

Full details for v13-beta1.

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] ShapeShifter499:
Your right something didn't flash correctly, clearing the cache didn't help. I had to flash my phone cleanly again. Thank you for the help.
[Magisk] Setialpha:
Quick heads-up:

I made a lot of fixes and improvements to the

nanomod-overlay

script (in the git repository, you can create a zip on your own until a new release arrives). Also it is now fully documented.

I also strongly encourage users to test the beta2 release and report any occurring issues.
[Magisk] CHEF-KOCH:
Thanks patcher finally works now on /system. Can't test magisk right now but I'll do.

There is in setup wizard one ) missing after Google (last entry). Besides that it works well now.
[Magisk] gimpy1:
Hello, all. Sorry to bother you, but I need help establishing my gmail account. I have both Magisk and Nanomod working properly, as far as I can tell. I have k-9 set up with two of my email accounts, but gmail will not work there now (it did last weekl, though). My google account is running thru micro g in the phone settings. I have downloaded the gmail app but google will not let me sign in to it saying that that account is already loaded. I keep getting security messages from google saying someone is trying to sign into my account (me).

I've tried all week trying to get it to work thru the gmail app, to no avail. The only way I can check my gmail is thru the gmail URL in the browser.

Anyone else had this problem? One of the security messages I get from google is that the mail client (k9) is not secure enough leaving me at risk.

Any thoughts, ideas?

Thx
[Magisk] CHEF-KOCH:
Use AquaMail it works well, yes I had the same issue but this is by far the best eMail app. It also works well with more than one account.
[Magisk] Setialpha:
In the GMail settings you can allow 'insecure' cllients. Google basically calls anything not Google insecure.

If you can't properly access your G Account from any app, you need to grant Account/Phone permission in Settings > Apps > [app] > Permissions.
[Magisk] DJ aliasz3d:
It's the same on Linux too with Thunderbird
[Magisk] gimpy1:
Thx, I have tried it, but still no success. Still get the different errors and it won't sync. In "The getting messages" and " just a sec", it just loads and loads ( with the circular arrow).

In the settings account, it says the account is not yet implemented. I'm not sure how to do that, since I thought that i was signed in, etc.
[Magisk] demonoidmaster:
Did you try the debloat script zip i attached for you a few pages back? It was to remove GCS remember
[Magisk] b4rgh3st:
Hi,

unfortunately I can't flash the setupwizard or the patcher through TWRP 3.0.2. Didn't try your other zips though.

recovery.log is attached.

TIA
[Magisk] Setialpha:
There's no log for the setup wizard. The patchr failed, because you didn't boot into the ROM once.
[Magisk] b4rgh3st:
Hmm..I'm pretty sure I did boot into my installed rom (at least 2 times).

And in the log is a part with the setup wizard:

Installing zip file '/external_sd/NanoMod-setupwizard-12.1.20170807.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
E:Can't execute '/tmp/updater': Exec format error
Updater process ended with ERROR: 255
I:Legacy property environment disabled.
Error installing zip file '/external_sd/NanoMod-setupwizard-12.1.20170807.zip'
[Magisk] Setialpha:
for the Patcher: it says

failed to initialize runtime

this likely has two causes:

dalvik-cache is not in place (this is done upon first ROM boot)

don't wipe cache and dalvik-cache prior to flashing the patcher, as dalvik-cache is required

LineageOS issue

the same issue is reported in a very few cases with other apps (like Termux) on LineageOS, aswell, no solution (yet) found for this rare bug, sadly

You may try 13.0-beta2 patcher, as that one can be flashed through Magisk Manager, aswell, maybe it works in-ROM if it doesn't work in-Recovery?

For the Setup Wizard: you've got an x86 device, AROMA only supports arm / arm64. I've updated the documentation accordingly. You'll have to manually create the configuration files on x86 / x86_64. The documentation has that covered, as well as example files, which can be easily edited.
[Magisk] b4rgh3st:
Thanks for the reply. Unfortunately on my device Magisk doesn't work since it requires Android 5+ while my old Razr I only supports 4.4.

Maybe I should try to patch it from my PC.

\edit: framework-patcher says *** patch-fileset: success

\edit2: would you mind to say some words what is meant with "system mode installation"? ("whether to force system mode installation, regardless whether Magisk is installed" in the documentation). I guess for me it doesn't matter since I don't have Magisk, right?
[Magisk] Setialpha:
It means that NanoMod should be installed into /system, even when Magisk is installed. If you don't have Magisk installed, it's irrelevant.
[Magisk] b4rgh3st:
Alright. What are the advantages and disadvantages of an installation into /system?
[Magisk] Setialpha:
Well, Magisk installation is OTA safe, can be temporarily disabled (mostly for testing purposes), /system partition doesn't get altered. /system installation doesn't need Magisk.
[Magisk] :
Got problem with latest beta in TWRP, getting error while it's trying to install sync apps, I attached log. Android 7.1.2.

View attachment recovery.log
[Magisk] ShapeShifter499:
I did not sorry
[Magisk] :
Nice!

Also looks like there are problems with NanoMod and Magisk v13.5, used v12.1 version of NanoMod full package, it doesn't go past splash screen. With just Magisk it's okay.
[Magisk] Setialpha:
I'll test it, thanks for the heads-up.
[Magisk] demonoidmaster:
Just remember, this zip is what I'm currently using, all i did was add GCS to it, so if you flash it it'll remove system apps such as Jello browser, Eleven music player, etc etc

So IF there's apps you really don't want to get removed then message me a list
[Magisk] Setialpha:
I thought I had replied, but it seems I didn't.

In the last screenshots microG complains, that no account with the given Mail/Password combo exists. I assume you entered something wrong? Or did you fully setup microG like written here?
[Magisk] Setialpha:
On a side-note: yes, NanoMod and Magisk v13.5 don't work together. I've already taken a logcat.

The issue looks like the same we had with the early Magisk v13.0 betas.
[Magisk] gimpy1:
Before the last beta/update I had the gmail account added as part of the k9 mail client and it worked fine. I think I changed something in my gmail that probably changed things, but whatever I did (don't know what), I can't fix it. Micro g says I have signature spoofing working and all the green boxes are checked. Magisk safety net is also working.

Except for the gmail "app" working, everything else seems to be working fine. I can still check my gmail thru the URL, but just not thru the app.

Thx, for checking.
[Magisk] b4rgh3st:
Alright..Here I'm again.

Even after successfully installing NanoMod via TWRP nothing has changed on my phone. There're no new settings or apps (no F-Droid for example). In a root browser I have a fdroid folder under /system/apps though.

This .nanomod-setup was used (and found during installation):

nanomod_microg=1
nanomod_fdroid=1
nanomod_apps=0
nanomod_play=2
nanomod_overlay=0
nanomod_zelda=0
nanomod_mapsv1=1
nanomod_init=1
nanomod_gsync=0
nanomod_swipe=1
nanomod_forcesystem=0

What can I provide to narrow down my problem?
[Magisk] CHEF-KOCH:
You said Magisk doesn't work for you currently, so you need to force nanomod_forcesystem=1 instead of 0 then it writes into it and you will see the microg settings app together with the other apps you allowed in your setup.
[Magisk] b4rgh3st:
Tried that, too, but with no success.
[Magisk] Setialpha:
What's the content of /system/.nanomod-list?
[Magisk] Setialpha:
Because you're on KitKat, that changed with Lollipop. I''l have to check.
[Magisk] b4rgh3st:
So, the other paths could have changed, too?
[Magisk] Setialpha:
Nope, the swipe path is just wrongly recorded (will fix it, soon), else it's ok.
[Magisk] b4rgh3st:
/system/priv-app is structured without folders in KK, too.
[Magisk] Setialpha:
I know, I'll need to figure out a sane way to achieve that in the installer.
[Magisk] demonoidmaster:
Or he could just update from KK to something more recent?, what's his device XD
[Magisk] Setialpha:
Razr I only has up to KK, but I'm there already, doing final tests.
[Magisk] demonoidmaster:
Surely someone on XDA must've made any kind of official or unofficial varying roms for that device, old or not there's always a way

If not well he should think about buying a new phone lol
[Magisk] Setialpha:
Nope, new XDA Razr I threads basically stop 2014.

Yes, it's old, but almost everything in NanoMod does support KitKat, I saw it as a challenge.

I made the installer believe I'm on KK and the result was what I expected, so now preparing beta3 for field tests.
[Magisk] b4rgh3st:
LineageOS11 is the most recent ROM for the RAZR I.

And why waste ressources when you have a phone that runs well and does everything you need?

edit: sorry for OT.

Btt: Thanks for your work [MENTION=4187311]Setialpha[/MENTION], I'll test the new beta today or tomorrow.
[Magisk] sudokamikaze:
[MENTION=4187311]Setialpha[/MENTION] just wanna ask you, i installed rom+supersu, then nanomod-patcher, microg, fdroid zip's

And Contacts app version is 1.4.*.* and now, i recived an update for it, after this i can't even open contacts because this app crashing

Do your project ship's contacts app by default or its rom issue?
[Magisk] evilvoice:
I can't seem to get the patcher working at all.

Samsung Galaxy Note 3

LP 5.0 Stock Rom

TWRP 2.8.7.0

https://drive.google.com/open?id=0Bz23CbKkUKMPVVNWU0RNdTgtbVE
[Magisk] EinsteinXXL:
I got a "odexed roms not supported" error message. Because of this I have deodexed the ROM (app, priv-app, framework folder) with Fulmics Deodexer, patched the services.jar with nanomod-patcher v13 beta 3 but stuck in bootloop (the result of deodexing not the patch). I dont no why, but I found a solution. Restored my nandroid backup and replaced the services.jar with the patched one. Tataaa! It works!
[Magisk] Setialpha:
No, there's no Contacts App included.
[Magisk] b4rgh3st:
Everything is in the correct place now. Thank you!

Another question: What's the point of the maps API v1?
[Magisk] Setialpha:
Some older Apps don't work without it.
[Magisk] Setialpha:
Quick heads-up:

KitKat is now marked as officially supported in the installers

for anything before KitKat a warning message is printed (as not officially supported)

added Google Sync Adapters for KitKat

improved a few installer functions

improved a few log messages

So 13.0 will land this weekend, the only remaining issue for now is that the patcher (still) isn't usable for a few people.

[MENTION=965544]evilvoice[/MENTION] could you try again with the 13.0-beta3 patcher? It might be an issue that's already fixed, so I'd like to ensure this, first.
[Magisk] EinsteinXXL:
[MENTION=4187311]Setialpha[/MENTION] Why does your patcher patches the services.jar? I aks this, because I found another patch (Tingle) which is modifying the framework.jar.

https://github.com/ale5000-git/tingle
[Magisk] evilvoice:
[MODULE/SYSTEM-MODE] NanoMod 12.1.20170807 (microG, pseudo-debloat, F-Droid + apps)

Here is the latest beta. Still coming up with errors. I changed to a newer recovery because it said there was an error executing binary so I went from TWRP 2.8.7.0 to 3.1.1.0.

https://drive.google.com/open?id=0Bz23CbKkUKMPRUx1RnJEZjQ2QXM

Side note: there are 3 patches, why are only 2 being applied? Just wondering. I'm willing to test anything you can possibly think of that is not allowing this to patch on device. At some point, I'll have to resort to patching from PC if it just isn't possible, which I may go ahead and do, just not push to device so I can test.
[Magisk] evilvoice:
[MODULE/SYSTEM-MODE] NanoMod 12.1.20170807 (microG, pseudo-debloat, F-Droid + apps)

Probably because the framework edits is for a permanent solution, while the services edit is so you can toggle it. There is an app that will turn it on and off. I don't know if it's included

Edit: the app isn't included but Settings.apk is patched to allow the toggle.
[Magisk] Setialpha:
Because haystack patches are built against services.jar, not framework.jar.
[Magisk] Setialpha:
The third patch is optional and is supported in upcoming 13.0 through a new setup variable (nanomod_sigspoofui).
[Magisk] Blackcrown:
Well, I patched my AOSP N ROM with tingle before flashing the Rom, Magisk and nanomod. It works.

While it's very comfortable to patch the ROM on the phone (Nanomod is very comfortable at all), I had my ROM opened in Android kitchen and it was only logical to patch framework.jar with tingle, let the studio put the ROM together again and flash it. That said, I am a Linux user.

Gesendet von meinem KFDOWI mit Tapatalk
[Magisk] meistr91:
Hi, I have same problem with new contacts app, and even going back to older version brings same crash...