yashsingh1/xdaforums huggingface dataset:
[Magisk] amg314:
Nandroid mostly is a microG installer.

Thus, if you have microG installed and it run OK on your device, you do not need upgrage Nandroid.

You could upgrade main microG components thru https://microg.org/download.html and/or any other apps (like Yalp, SkyTube, etc).
[Magisk] :
I had an issue earlier after updating my vendor, which somehow resulted in fakestore disapearing from the device. Its still listed if I look it up in the terminal, but it disapears from the microG checklist. Last time f-droid disapeared aswell, but this time it didnt. I updated my phone earlier today, and it disapeared that time to, but forgot to save the log before long after, so I didnt bother.

Now though, Ive flashed the new vendor again, and now.I have a log. Though adb never got any reading on the device, so Ive only got what the phone could give me.

Could you look at it, and see if youll find anything?

Thanks
[Magisk] PoochyX:
Why not just use Google play services save you the trouble

([emoji3590]09-09-18[emoji813])
[Magisk] dhacke:
Where is the sense of this comment? It doesn't help [MENTION=8828390]howaboutno[/MENTION] in any way.

He has a problem with microG/FakeStore and i guess he wants MicroG further because it seems that he had it before.
[Magisk] PoochyX:
Cause modifying phones causes issues at times im just trying to direct him to a less hassle solution

([emoji3590]09-09-18[emoji813])
[Magisk] dhacke:
I think this is worst solution regarding privacy. Problems with MicroG so back to Spyware Play Services:eek:

But that's another discussion and probably OP. So i think we should here and wait what [MENTION=8828390]howaboutno[/MENTION] says (if he want).
[Magisk] lutably:
Patched Play Store Error DF-DFERH-01

Hardware: Google Pixel (sailfish)

OS: LineageOS 16.0 with MicroG

NanoDroid: NanoDroid-microG-22.3.20190805

Recovery: TWRP 3.3.0

Everything seems to have gone fine with the Setup Wizard and installation, but I am unable to access the Play Store.

I was prompted to sign into my Google account, which I did. Then, I simply get a message when trying to access the Play Store that says "Error retrieving information from server. DF-DFERH-01"

I have tried clearing the cache and data for the Google Play Store app, removing and re-adding my Google account, and giving the app various combinations of permissions. None of these seem to solve the error.

I'm happy to provide additional information and can use tools like TWRP, Magisk, ADB, as necessary.
[Magisk] :
Dont let him bother you. Its not the first time he's been at me with some nonesense..

Yes, even pico, the smallest gapps package is just too much for me, especally after discovering what a godawfull place thr internet is for privacy and security..

I just want a solution, if there is any for this particular issue of mine.
[Magisk] dhacke:
Regarding to your problem:

I have two ideas. First i would try to install FakeStore again via apk from the microG site or via F-Droid.

When that doesn't work install nanodroid zip again (with "1"at the FakeStore entry by the nanodroid setup file).

Mayby the nanodroid installer repairs the broken parts of FakeStore/microG then.
[Magisk] :
I've reflashed it both times, which fixes the issue, untill I update the rom, or the vendor. Though it havent always been like this. Never though about installing it from f-droid. Ill try that instead, next time.
[Magisk] DrUnknownEMC:
Usually a reboot fixes this issues for me.
[Magisk] Setialpha:
22.4.20190811 "Château Picard"

Hi everyone,

version 22.4 Codename Château Picard is now available.

Highlights

updated Aurora Services to 1.0.4 to fix issues with installing APKs via Aurora Store/Aurora Droid when Aurora Services is used as installation backend

many thanks to TanyaEleventhGoddess who devoted some of her free time for a major refactoring of the build-package script

starting with 22.4 all releases now also ship a package report file "NanoDroid-Report-${VERSION}" which contains everything you wanted to know about NanoDroid (and way too much more)

Reminder

Just two general reminders:

known Issues and fixes are listed here: NanoDroid#Issues.

Bug report without logs (TWRP/installation log or logcat) are pretty useless, as no one can see what's going on and thus not help you.

Full ChangeLog

## 22.4.20190811 "Château Picard"

### Bugfixes

* build-package
* fix various minor issues @TanyaEleventhGoddess

### General Changes

* build-package
* major refactoring @TanyaEleventhGoddess
* new envvar `BP_USE_WGET=1`: use `wget` instead of `curl` for downloads @TanyaEleventhGoddess
* new envvar `BP_DEBUG=1`: print debug information during downloads @TanyaEleventhGoddess
* dynamic date in created packages @TanyaEleventhGoddess
* new switch `report`: create package report with (way too much) information about NanoDroid
* will also be auto-created when building `all` packages
* reports get their SHA256 checksum and GPG signature

* Installer
* `GoogleCalendarSync` is the same APK across all Android versions, thus it's now only downloaded/included once

### Updates

* automatic
* Aurora Services (1.0.4)
* Bromite System WebView (76.0.3809.100)
* OsmAnd+ (3.4.)
* Simple Calendar (6.5.7)
* Termux (0.73)

* manual
* Google Play (16.1.23)

Download links

Download from Nanolx.

Bug reporting

In case of errors, please provide

/data/media/0/MODID_log_INSTALLDATE

/data/media/0/MODID_twrp_INSTALLDATE

SysTest package logfile

logcat (if applicable)
[Magisk] mongo0:
Is playstore app not included anymore?!
[Magisk] garylawwd:
It is. It either needs to be added in config file or setup wizard in aroma twrp
[Magisk] mongo0:
I just updated and its gone.

I have nanodroid_play=10 in the config (.nanodroid-setup) ?<!
[Magisk] Setialpha:
Then you've got a different configuration file somewhere which is used instead. See also: https://gitlab.com/Nanolx/NanoDroid/issues/82
[Magisk] mongo0:
thanks for the replies. However the other locations are clean, no other config files..

After I reinstalled nanodroid with nanodroid_play=31 (no clean install / uninstaller not used) FDroid now wants to update Playstore which isn't installed/showing up.

And Aurora tires too update microG services core to Jun 19 version which seems outdated

Maybe I should have made a full wipe before upgrading nanodroid...
[Magisk] marcdw:
Check your system carefully for either Play Store or FakeStore (both have the same package name, FYI), via Settings and/or root-enabled file manager. F-Droid is not going to offer an update to something that doesn't exist.

Aurora Store gets things from the Play Store (nowhere else afaik??) so it's not showing an actual update to microG but to Google Play Services. Those, too, have the same package name. Were you referring to Aurora Store or AuroraDroid? That part's not clear.

LG G3 D851, PAC-ROM 6, MultiROM, XDA Legacy
[Magisk] Roman_RO:
MicroG won't let me add my Google account. The rom I'm running has spoofing support, but there's more steps that I need to do before I can get this working and im not sure what those steps are.

Sent from my..........
[Magisk] amg314:
Google acconts should be removed thru Settings before microG installing.

If you did not remove your account, you may try delete it after microG installing using SQLite Editor https://play.google.com/store/apps/details?id=com.speedsoftware.sqleditor

You can find accounts db on the following paths: /data/system_ce/0/accounts_ce.db and /data/system_de/0/accounts_de.db.

After that you should create the same account in a common way.
[Magisk] mongo0:
hm but I have F.-Droid suggesting an update to Google Play Store (by google): 16.1.23-all (8/11/9) from Nanolx Repository but when I press update I get "Error Installing Google Play Store Error: -7 A previously installed package of the same name has a different signature than the new package (and the old package's data was not removed)"

I wiped cache of FakeStore (com.android.vending) but Fdroid is still offering to install (*update)Google Play app

I meant Aurora Store or the app you get when setting play=31 (I used 10 since ever....)
[Magisk] marcdw:
Yes, that's normal. F-Droid sees the package name that FakeStore uses, which is the same as Play Store, thus offering up an update. Since FakeStore is just that, a fake store, trying to update it will fail.

FakeStore is essentially a placeholder. There are some apps that look for the presence of Play Store but do not otherwise use it. That's the purpose of FakeStore.

So the question is do you want the Play Store? If so you'll have to get rid of FakeStore. I suppose redo your config and flash NanoDroid to install the real store. If you don't want the Play Store (don't need to purchase apps or do license checking) then just ignore the updates shown in F-Droid. F-Droid allows you to ignore updates via a particular app's three-dot menu.

Moto G5S Plus XT1806, OmniROM 8.1.0, microG (NoGapps), MultiROM, XDA Legacy
[Magisk] ydd0ras:
Strange, just tried 22.4. The same issue. The only version that I can successfully flash on my Mi 9T is v21.0.20190601. All flashing versions above this version always ending with same error message.
[Magisk] Roman_RO:
I'm trying to log in to my Google using g Aurora store but its say check password. The pw I'm entering is the right one!

Sent from my..........
[Magisk] githyanki:
Of you use 2 factor authentication, you'll need to create an app password for Aurora.
[Magisk] Roman_RO:
Would I download something like a app locker and set a password for Aurora?

Sent from my..........
[Magisk] githyanki:
Search Google for directions, but in general, log into your account and security settings, add app password.
[Magisk] Roman_RO:
I can't log into my account because it says Google play services isn't installed. I done another wipe and reinstalled my rom then I flashed magisks then booted rom and turned on spoof settings then I downloaded nanodroid v22.4 20190811 zip and flashed in twrp. There was alot of apps installed Aurora store,Aurora severices,and MicroG service core, plus slot of other apps. I went to self check in microG settings and under Sig spoofing there's 3 boxes the 1st box is checked, under Installed Packages there are 5 check boxes, boxes 1,3,5 are checked u der permissions granted all 5 boxes are checked. I'm not sure how I can set a app password if I can't log into Google.

Sent from my..........
[Magisk] githyanki:
Using web browser, not in the system.
[Magisk] Roman_RO:
I tried that it won't let me sign in for some darn reason. This is getting aggravating I'll try again tomorrow.

Sent from my..........
[Magisk] marcdw:
[MENTION=9736821]Roman_RO[/MENTION], going by your other post I take it you just flashed NanoDroid and got whatever it gave you. Maybe stuff you don't want or need. If at all possible I'd suggest starting over and flashing/running the configuration wizard first. There you can pick and choose what you want/need. Then flash NanoDroid.

If your TWRP doesn't support AROMA the docs will tell you how to create a config file manually.

LG G3 D851, Candy7 v6.0 ROM, Google free - no microG, MultiROM, XDA Legacy
[Magisk] cnat:
edit: apps hung on launch. restarted twice; didnt work at first, then worked fine.
[Magisk] SH1M4BD3:
[MENTION=4187311]Setialpha[/MENTION] Sir the setup zip won't work on my Mi 8 tried different versions of twrp, and Orangefox still won't load the aroma setup, its always hang and freeze and need to reboot manually...
[Magisk] Brandon9231:
Is there anyway to get the libs for Swype installed with this? I use the aosp keyboard and it doesn't work without gapps unless its already put in a ROM (rare) or you do it yourself. I'm pretty sure there isn't a module that already does this (please point me to it if I'm wrong) and this seems like it'd go along well with this module. I'm just bringing this up here because I'm not sure if there's a way to do it systemlessly(?) to not trip safetynet by changing my system.

Here's a link to the files I personally use: https://app.box.com/s/g0x7ei8diuxbvfhdfx7s1f3p8n38nl6m I'm pretty sure they're only for arm64 devices on lollipop+ and are probably outdated since I got them from an old post in the microg thread but they work for me once I set their permissions to 644 and paste them in their respective folders. Newer versions/those for other devices can probably be pulled from any gapps package but I just haven't bothered, though I'd be happy to get them if it meant this could be implemented into NanoMod.
[Magisk] gimpy1:
I've used Swype for the last couple of years, before that I used Swift Key. I found an old swift key apk this afternoon and an now using it. I've got to have a swipe key board, but don't really like the Google one.
[Magisk] Shadow53:
The swipe libraries are architecture-dependent, so you are right about that. Until it's added in NanoMod, you can use https://shadow53.com/no-gapps/downloads/#google-swipe-libs. The zips will modify /system, so I don't know if they will affect SafetyNet as I don't use anything that depends on that.
[Magisk] pbeckmann:
Hey,

just as a small information. I wanted to use the microg and fdroid from NanoMod but not the Apps.

I experienced a long boot time with the full package and decided to try just the smaller fdroid and microg package.

Actually it performs really well. The boot time is dramatically less than with the full package and PlayStore and FDroid are working as expected.

So thanks for your work :*

P.S. You can GitLab push changes from repo instantly to GitHub. You just should change the description on GitHub. So everbody knows that they can't contribute at GitHub. And pls then disable the issue tracker at GitHub ^^ #justMyTwoCent
[Magisk] Brandon9231:
Thanks, instantly bookmarked your page :highfive:

I wasn't passing safetynet anyway so I tried the swipe zip and all is well. Definitely makes nightlies a lot easier ;)
[Magisk] Setialpha:
To catch up the last two, three days in a summary:

1) The github repo is now a mirror of the gitlab repo.

2) I may add swipelibs as optional part.

3) Magisk installed and NanoMod in System Mode does not cause any additional issues.

4) SafetyNet is known to fail when NanoMod is installed as Magisk Module, that's a bug in Magisk v13 beta.

5) for every other issue directly related to NanoMod post logcat and/or recovery log.

6) for microG related issues or questions on it, read the microG docs and use it's own thread.

7) I'll have a look at GSync for MM.

On a side note: the layout for .nanomod-apps and .nanomod-setup files is changed in v11; in the git version is currently no check for the old syntax, I'll add it, though.

If you don't know what that means, ignore it; else take a look at the example files and update yours.
[Magisk] Setialpha:
Quick update:

SafetyNet passes again with NanoMod as Magisk Module with unofficial beta 20170709 (the bug in Magisk has been fixed)

I made several fixes to the new configuration file handling in installers (including migrating old format files to new format) and pseudo-debloat feature

So... I'll release a 11.0-beta1 within the next 24 hours.
[Magisk] abacate123:
Thanks :)

If you need some tester, call me.
[Magisk] sudokamikaze:
Hi, using your NanoMod with Pixeldust for mako, (Flashed Nanomod-patcher then Nanomod-mircoG then Nanomod-fdroid) but i have problem.

Today i needed to recive an important SMS for me, but i didn't recived it because "SMS/MMS" app is missing, when i installing OpenGapps this app appears in menu, pls fix it
[Magisk] Setialpha:
I need more informations, what version did you use, did you use the default setup? Did you install as Magisk Module or in System Mode?

The pseudo-debloat feature is not active by default for the microG package (and not present in the F-Droid package). It also only works as Magisk Module.
[Magisk] Setialpha:
11.0-beta1

Version 11.0-beta1 is now available. This release brings several fixes and improvements compared to 10.0.

Full ChangeLog since 10.0

* General Changes
* Full, microG, F-Droid package
* if using fallback configuration during installation print the information accordingly
* change syntax for `.nanomod-apps` file
* existing configuration files will be migrated to new format
* change syntax for `.nanomod-setup` file
* existing configuration files will be migrated to new format
* simplify handling fallback configuration
* Full, microG package
* if using fall back `nanomod-overlay` configuration remove it after installation
* the `nanomod-overlay` script will create it during runtime, if required
* remove all launchers from list of pseudo-debloated apps by default
* several fixes to `nanomod-overlay` script
* add optional `Swipe` libraries, controlled by `nanomod_swipe=[0|1]`
* make `/data` the very last directory to look for configuration files
* uninstaller:
* fixed restoring unpatched `services.jar`
* on-device framework-patcher:
* fixed that it accidently backed up the patched `services.jar` instead of vanilla
* Updates
* Play Store (8.0.26.R)
* Simple Gallery (2.12.1)
* Open Camera (1.38.2)
* New Pipe (0.9.9)
* GNU Nano (2.8.5)
* OpenLauncher (0.5.3)
* Kernel Adiutor (0.9.71.1)

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] gimpy1:
This is still new to me. I have spent the last two - three days working on getting everything setup. I still cannot pass safety net. My question now concerning the update, so I just have to install Nano-mod ? Or install all five of the updates in your link?

One other quick question (for now), it seems everytime I reboot, I have to re - set up most all of my settings? Will I have to redo/reconfigure all of my apps such as my contacts which I somehow got transferred over this morning. :confused:

Is there some way not to lose everything?
[Magisk] Setialpha:
5? Nope. The big/Full package contains everything, the F-Droid and microG packages are subsets of the Full package. The other two are are the framework patcher and uninstaller.

To pass SafetyNet you need atleast Magisk beta 20170709 or wait for official v13, which will come in a few hours. Or install in system mode.

No, it's not normal to loose all data and I never heard of such an issue. But without logcat I can't say anything.
[Magisk] sudokamikaze:
Magisk version, version i installed is 10.0.20170701
[Magisk] abacate123:
[MENTION=4187311]Setialpha[/MENTION] just wondering, can you see if you can get the Google play games app working in your side? I just can't over here, dunno if it's a known issue, it shows a white screen here.
[Magisk] Setialpha:
Play Games is not supported by microG
[Magisk] Setialpha:
what gives

ls /magisk/NanoMod/system/app

?
[Magisk] HeinJanMaat:
First of all, thanks for your work :good:

NanoMod-11.0.beta1 won't install with Twrp blu_spark.v39

Archive: /sdcard/Erbse/NanoMod/NanoMod-11.0.beta1.zip
inflating: .nanomod-overlay
inflating: .nanomod-apps
inflating: .nanomod-setup
/tmp/updater: /data/.nanomod-setup: line 1: nanomod.microg=1: not found
...
/tmp/updater: /data/.nanomod-setup: line 10: nanomod.gsync=0: not found
++ migrating /data/.nanomod-setup to new format
sed: : No such file or directory
sed: can't move 'IDLXNG' to '': No such file or directory
/tmp/updater: /data/.nanomod-setup: line 1: nanomod.microg=1: not found
...
/tmp/updater: /data/.nanomod-setup: line 10: nanomod.gsync=0: not found
/tmp/updater: /data/.nanomod-setup: line 1: nanomod.microg=1: not found
...
/tmp/updater: /data/.nanomod-setup: line 10: nanomod.gsync=0: not found
/tmp/updater: /data/.nanomod-apps: line 2: HackerKeyboard: not found
...
/tmp/updater: /data/.nanomod-apps: line 10: Termux: not found
/tmp/updater: /data/.nanomod-apps: line 11: syntax error: unterminated quoted string
Updater process ended with ERROR: 2
I:Legacy property environment disabled.
I:Install took 4 second(s).
Error installing zip file '/sdcard/Erbse/NanoMod/NanoMod-11.0.beta1.zip'

Downgrade TWRP to v38 and everything is working fine as usual.

Same for TWRP v39 with NanoMod-10.0.20170701

Nice day/good night everyone

1+ 3T

Varun Date's RR

Magisk 13.1
[Magisk] Setialpha:
Seems the configuration file format migration fails. I'll have a look.

Edit: I guess I've found both causes. Will push beta2 later today.
[Magisk] sudokamikaze:
mako:/system # ls /magisk/
NanoModfdroid NanoModmicroG

mako:/system # ls /magisk/NanoModmicroG/
auto_mount module.prop post-fs-data.sh system
[Magisk] :
Is your phone compatible with aroma? Not all phones are. Create a config file and flash full nanodroid zip, or just f-droid package or microG or whatever it is that you wish to flash.
[Magisk] nodeofollie:
Can someone explain in a little more detail on how to set font using Terminal? So far, I can get to where you see all the font names, when I enter set [NintendoLabo] into emulator, nothing happens. All the other commands s or --set do not work for me
[Magisk] SH1M4BD3:
.. just f-droid package or microG or whatever it is that you wish to flash.[/QUOTE]

I usually use patched play store, so that purchased apps can load , as I'm sure its arm64 ..it should be work isn't?
[Magisk] :
I honestly have no info regarding which devices or architechtures has suport, or is suported by aroma, afaik, aroma isnt exacly something new either. Create a .nanodroid-setup file, and write the following

nanodroid_play=10

I put mine in /data, but there are other places that works aswell. Like the folder where zip is, but personally I had little success with that particular placement..

Have a look in the documentation for futher info if your interested.

Edit: by flashing microG zip and having this config, you will then have what you asked for.
[Magisk] SH1M4BD3:
Done, read the doc, created manually the setup, thanks everyone
[Magisk] parasnip:
Don't install the "Full"Package as the additional bloatware apps will be installed as system apps. It wasn't event possible to uninstall them with root properly. Now I'm stuck again in a bootloop. Thanks for this!
[Magisk] githyanki:
You can select not to install them at all, or to install only a select few. You don't have a complete setup file. Here's the rest of the options. (Everything disabled)

nanodroid_fdroid=0

nanodroid_apps=0

nanodroid_overlay=0

nanodroid_zelda=0

nanodroid_mapsv1=0

nanodroid_init=0

nanodroid_gsync=0

nanodroid_swipe=0

nanodroid_forcesystem=1

nanodroid_bash=0

nanodroid_nano=0

nanodroid_utils=0

nanodroid_fonts=0

nanodroid_play=00

nanodroid_nlpbackend=0000

nanodroid_microg=0