[MODULE/SYSTEM] NanoDroid 23.1.2.20210117 (microG, pseudo-debloat, F-Droid + apps)

Search This thread

Oswald Boelcke

Forum Moderator / Recognized Translator
Staff member
Afaik you need Magisk for MicroG...

Edit: Or do you mean flashing NanoDroid via TWRP and not in Magisk?
I'm convinced @kurtn exactly means that. Personally, I always flash NanoDroid modules only via TWRP and never in Magisk Manager.
 
  • Like
Reactions: kurtn

HippoMan

Senior Member
May 5, 2009
1,577
430
113
Hippoland
I'm wanting to at least try to install the microG version of lineageOS on my OnePlus 7Pro (and yes, I know that it might not work). The final step of the instructions (after installing TWRP, etc.) is to flash NanoDroid. However, when I go to the NanoDroid download site, I see numerous zip files, and I'm not sure which one (or ones) should be installed via this "flash NanoDroid" step ...

This is the list of all the NanoDroid zip files to choose from ...

Code:
NanoDroid-23.1.2.20210117.zip
NanoDroid-BromiteWebView-23.1.2.20210117.zip
NanoDroid-Google-23.1.2.20210117.zip
NanoDroid-OsmAnd-23.1.2.20210117.zip
NanoDroid-fdroid-23.1.2.20210117.zip
NanoDroid-microG-23.1.2.20210117.zip
NanoDroid-patcher-23.1.2.20210117.zip
NanoDroid-systest-23.1.2.20210117.zip
NanoDroid-uninstaller-23.1.2.20210117.zip (yeah, I know this isn't one,
                                           but I'm just including it in this list
                                           for the sake of completeness)

Thank you for any suggestions.
 

papei

Senior Member
Jul 11, 2012
168
27
58
Basel
The first one mentioned (NanoDroid-23.1.2.20210117.zip) is the complete package. In addition to MicroG and F-Droid, it has a number of useful open source tools. You might not need everything in the package, but it is the easiest to install.
 
  • Like
Reactions: HippoMan

drahtwurst

Senior Member
Nov 17, 2014
89
9
38
Berlin
i am trying to get a gsf sensitive app to run. formerly it complained wanting to be installed from play store. im on android 11 custom signature spoofing rom, root, magisk22 and safetynet fix 111 installed. just flashed the microg package. i guess i am suppossed to check every checkbox in micro g, so i did. wifi+location enabled+working.

this (and no other) app wont download in aurora store. safetynet check in magisk fails. with or without own google account. pls someone tell me what to do.
 
Last edited:

diNovoM

Senior Member
Aug 30, 2013
109
31
48
this (and no other) app wont download in aurora store. safetynet check in magisk fails. with or without own google account. pls someone tell me what to do.
And whats that app? Some apps require a google acc even though free and install. in browser before while logged in (same as paid) is required, else you could dl them on other market.
Safetynet is st different, its known broken for some while though latest commits may ffixed it? https://github.com/microg/RemoteDroidGuard/issues/24
 
Last edited:

drahtwurst

Senior Member
Nov 17, 2014
89
9
38
Berlin
any app and with or without own google account wont download. take medizinfuchs if you want that is not gsf dependent. or for instance binance - gsf dependent. no downloading.
with google playstore there is no other precaution, just download+install. dont know what you mean by
in browser before while logged in (same as paid) is required
if i download from another market the banking app wont work, thats what i see and the bank support confirms.
 

diNovoM

Senior Member
Aug 30, 2013
109
31
48
any app and with or without own google account wont download. take medizinfuchs if you want that is not gsf dependent. or for instance binance - gsf dependent. no downloading.
with google playstore there is no other precaution, just download+install. dont know what you mean by
Did you read https://gitlab.com/AuroraOSS/AuroraStore/-/wikis/Troubleshooting-&-FAQs f.e. and esp the part about account/paid apps. You need to buy/dl in browser, then you can use it aurora store. Alt. you could use mod. Play Store alone (without all those google services aka Framework). Check some details here https://github.com/microg/GmsCore/issues/617
if i download from another market the banking app wont work, thats what i see and the bank support confirms.
I doubt that's caused by the market (if its only a google mirror market, not modding them). Banking app will most likely fail due to safetynet currently not validating. But those other apps like medizinfuchs can be perfectly dl and used if using another market or install via browser first or mod. Play store.

Edit: I forgot - do you use FakeStore? Well in any case read 2nd link carefully with all answers there, it will answer your question i can tell u'll have.
 
Last edited:
  • Like
Reactions: drahtwurst

drahtwurst

Senior Member
Nov 17, 2014
89
9
38
Berlin
just flashed the microg package
--->
do you use FakeStore?
----> NO
as i said: no download was possible in aurora. NONE! thanx for the link:
AuroraStore Troubleshooting-&-FAQs helped since it was caused by the market default settings i needed to change.
no
need to buy/dl in browser
!
with magisk22: safetynet fix 111 is not needed. the safetynet check fails in magisk but banking+navi works now, even after reboot and removing fix111. that was what i was trying to accomplish (y)
 

starbright_

Senior Member
Apr 11, 2010
1,270
206
83
I tried to spoof signature of an Android 11 (Galaxy S10). As recommended I installed it as a module out of TWRP. Log looks fine at first glance. (It was a longer list of messages with no errors/warnings).
After the required reboot it comes into a boot loop. (There is some strange thing that S10 with Magisk enabled has to boot in "recovery mode"). After some boot-attemps it finally boots up, but with neither Magisk nor Spoofing enabled (no wonder - as this is withouth that magic key-pressing).
I though copy back the previous services.jar (in TWRP) will help but that seems not to be the case.
 
Last edited:

FMAranda

Senior Member
Jun 25, 2011
747
243
73
São Paulo
I tried to spoof signature of an Android 11 (Galaxy S10). As recommended I installed it as a module out of TWRP. Log looks fine at first glance. (It was a longer list of messages with no errors/warnings).
After the required reboot it comes into a boot loop. (There is some strange thing that S10 with Magisk enabled has to boot in "recovery mode"). After some boot-attemps it finally boots up, but with neither Magisk nor Spoofing enabled (no wonder - as this is withouth that magic key-pressing).
I though copy back the previous services.jar (in TWRP) will help but that seems not to be the case.

The patcher didn't worked for me either, so I manually patched the ROM and got microG to work. It's really easy and, since the procedure is about patching services.jar through a Magisk module you create, it persists after ROM updates: https://forum.xda-developers.com/t/signature-spoofing-on-unsuported-android-11-r-roms.4214143/
 
  • Like
Reactions: starbright_

OneWayGamer

Senior Member
Mar 31, 2017
262
85
38
Can someone help me with Dead By Daylight Mobile Google Account login? I have MicroG package with Platstore. But in Dead by Daylight Mobile, I can't login with my Google account (This game doesn't use Google play games,direct Google account login), so if anyone can provide fix, please do
 

starbright_

Senior Member
Apr 11, 2010
1,270
206
83
The patcher didn't worked for me either, so I manually patched the ROM and got microG to work. It's really easy and, since the procedure is about patching services.jar through a Magisk module you create, it persists after ROM updates: https://forum.xda-developers.com/t/signature-spoofing-on-unsuported-android-11-r-roms.4214143/
Do I have to install both for spoofing? I didn't deinstall playstore/services first. After booting screen flickers, so I did something wrong.
 

FMAranda

Senior Member
Jun 25, 2011
747
243
73
São Paulo
Do I have to install both for spoofing? I didn't deinstall playstore/services first. After booting screen flickers, so I did something wrong.

Since the patch is made by modifying the services.jar directly and outside the ROM (the ADB part is just to connect and pull the file from the file system, it doesn't do anything to the ROM yet), it shouldn't matter if you have already flashed Nandroid or not.

I recommend you to do the procedure of that thread first, but only flash the spoofing patch after you have installed Nandroid, because it'll handle clearing play services out of your ROM.

And, fyi, you don't need to flash the microG\_AVDx86api30\_magiskMaRViN.zip. This is a microG package but you'll use Nandroid instead, so microG\_AVDx86api30\_magiskMaRViN.zip not needed.

In short: create the patch following the tutorial from the link -> flash Magisk (if your ROM doesn't have it) -> flash Nandroid from this thread -> flash the spoofing patch.
 
  • Like
Reactions: starbright_

starbright_

Senior Member
Apr 11, 2010
1,270
206
83
In short: create the patch following the tutorial from the link -> flash Magisk (if your ROM doesn't have it) -> flash Nandroid from this thread -> flash the spoofing patch.
Thanks. I used the time to just install spoof...zip. The result was exactly or very simular from what happens if you install Nanodroid Patcher via Magisk. But I will try your how-to ... and it works! Thanks a lot.
 
Last edited:

FMAranda

Senior Member
Jun 25, 2011
747
243
73
São Paulo
Thanks. I used the time to just install spoof...zip. The result was exactly or very simular from what happens if you install Nanodroid Patcher via Magisk. But I will try your how-to.

If you tried other methods, you might have done something to your ROM that's preventing anything else to work properly. You should consider do a clean flash of your ROM and then to the patching.
 

drahtwurst

Senior Member
Nov 17, 2014
89
9
38
Berlin
after making banking possible with aurora store using this advice, it failed again. this time aurora refused to update. maybe it is connected to installing vanced micro g package for youtube vanced later.

it helped me to toggle 'Download apps in internal storage' in Settings > Downloads off and on again (in aurora). this problem/workaround has not been answered yet in the Troubleshooting & FAQs.
 

starbright_

Senior Member
Apr 11, 2010
1,270
206
83
If you tried other methods, you might have done something to your ROM that's preventing anything else to work properly. You should consider do a clean flash of your ROM and then to the patching.

You method: using nanodroid-microG and the manual created spoof.zip works for me. Thank you!
I didn't deinstall any Google stuff (Playstore/Services). But they seem to be disappear. Have they been deinstalled by the nanodroid package?
I am wondering why nanodroid doesn't install an FDRoid compatible version. Not sure about, but won't that create trouble in case of updates? Do I have to flash new Nanodroid packages for update that?
 
  • Like
Reactions: FMAranda

FMAranda

Senior Member
Jun 25, 2011
747
243
73
São Paulo
You method: using nanodroid-microG and the manual created spoof.zip works for me. Thank you!
I didn't deinstall any Google stuff (Playstore/Services). But they seem to be disappear. Have they been deinstalled by the nanodroid package?

Nice! :)
Yes, the nanodroid package clears any google apps/services related stuff it finds in your ROM.

I am wondering why nanodroid doesn't install an FDRoid compatible version. Not sure about, but won't that create trouble in case of updates? Do I have to flash new Nanodroid packages for update that?

That's because the nanodroid-microG package doesn't contain F-Droid. For that, you can flash the nanodroid-fdroid package or just download the official apk from their website (https://f-droid.org/F-Droid.apk).

1615128761080.png


You can read more about the available modules here: https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/Packages.md
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Im in the exact same position as you, with exactly the same device and the exact same problem.
    Im almost going insane trying to get this to work all day!

    The Installation of "NanoDroid-FULL" of "NanoDroid-microG" does only result in bootable device if:
    • No .nanodroid-setup file is present
    • OR "nanodroid_play=01" in the .nanodroid-setup file
    The Installation of "NanoDroid-FULL" of "NanoDroid-microG" does result in unbootable device and boot loop if:

    • A .nanodroid-setup file is present
    • AND "nanodroid_play=10" in the .nanodroid-setup file

    @Setialpha Can you please help? I saw that this issue https://gitlab.com/Nanolx/NanoDroid/-/issues/176 got closed when its unfixed and still relevant.
    Tried alternative installers? Like https://github.com/friendlyneighborhoodshane/minmicrog_releases/
    1
    Hurrah!!! Thank you a lot!!! It worked I did not realise that I can tell Magisk where the files are stored - so Magisk excepted to flash files which have been stored on the external SD Card. Even the patcher worked!!! I'm so happy finally something worked after the mess with the Bootloader and the recovery
    1
    Please allow me to directly seek for your expertise as unfortunately the XDA search is still broken yet. And a web search didn't provide a suitable answer. And actually, my question is only out of curiousity as everything is perfectly working.

    When has the Google Play Store modified/patched by @Setialpha last been updated.

    My latest update is from end of July 2020; version as shown in screenshots. The Nanodroid F-droid repo is added to F-droid and was last checked for updates three days ago. However, I'm not even sure if the modified GPS is available via that repo.
    View attachment 5256827View attachment 5256829View attachment 5256831View attachment 5256833
    I had the same issue, when freshly installing last nanodroid 23.1.2.20210117. I fixed it by simply removing the fdroid repo and adding it back.

    I had issues on microg asking for background location permission and since the fix was to install gmscore.apk as a user app the easiest way (and the way it worked) was to update the app via the fdroid repo.
    I guess there is something misconfigured in microg repo in nanodroid.
    1
    nanodroid google sync does not support android 11.

    any solution or alternative?
    1
    By flashing in recovery? Because as I mentioned it didn't work through Magisk. However my question was regarding a more automated updating process - I'm okay to wait (for Aurora to be updated) if that means Magisk will remind me (of Nanodroid updates).
    No, Magisk will never remind you as the NanoDroid modules aren't part of the Magisk repo. Personally, I always flash my desired NanoDroid modules via TWRP and never by Magisk as there were severe issues in the past (maybe device, maybe ROM related IDK). And I assess to just boot into recovery and to flash it from there not to be a big issue.
  • 346
    NanoDroid

    NanoDroid is a installer for various OpenSource related things, most noticably microG and F-Droid. It supports direct /system installation, both devices with or without A/B partition scheme, aswell as Magisk Mode (module) installation. It also includes several tools (eg. GNU Bash, shell utilities, more), scripts, fonts, sounds and additional features (system debloating, init scripts, automatic logcat creation), aswell as a companion F-Droid Repository.

    Furthermore it allows the user to do fine-graded installations using configuration files, which allow to choose what to install, or if several alternatives are available, which of them, see "Alter Installation" in the full documentation (link at the end of this post).

    In order for full microG experience NanoDroid contains a modified Play Store which allows (in-)app-purchases with microG, which would normally not be possible. It also tries to remove all previously installed GApps on it's own. For ROMs without builtin signature spoofing support NanoDroid includes an on-device Patcher which tries to patch your ROM from TWRP.

    Versions until 15.1 were called NanoMod, starting with 16.0 they're called NanoDroid.

    NanoDroid does now have a companion F-Droid Repository for easy updates of Play Store (patched with (in-)app-purchase support) and MPV builds Repository Info-Page

    Current Release

    Stable: 23.1.1.20210117 "BusyCompat"
    Beta: --- (---)



    Supported Android Versions

    NanoDroid officially supports the following Android versions:

    • 4.4 / SDK 19 (KitKat)
      • System Mode only (Magisk does not support KitKat)
    • 5.0 / SDK 21 (Lollipop)
    • 5.1 / SDK 22 (Lollipop)
    • 6.0 / SDK 23 (Marshmallow)
    • 7.0 / SDK 24 (Nougat)
    • 7.1 / SDK 25 (Nougat)
    • 8.0 / SDK 26 (Oreo)
    • 8.1 / SDK 27 (Oreo)
    • 9.0 / SDK 28 (Pie)
    • 10.0 / SDK 29
    • 11.0 / SDK 30 (R)
      • Patcher does not work from TWRP
      • Patcher works from Magisk if your ROM's services.jar already contains classes.dex
      • Deodex Instructions
    earlier versions will never officially be supported (you may still report bugs, though).

    Future versions will be officially supported, eventually.

    Summary

    NanoDroid can be installed as a Magisk Module or directly to /system, though a bit functionality is only available with Magisk. It must be installed from TWRP!

    NanoDroid includes

    • microG and it's companions
      • on-device framework-patcher for microG support (signature spoofing)
    • F-Droid and it's privileged extension
      • modified Play Store to allow (in-)app-purchases with Magisk
        • alternatively Aurora Store can be installed instead
    • custom init scripts
    • pseudo-debloat feature
    • several Open Source applications
      • include replacements for the pseudo-debloated applications
      • full list of included applications
    Packages

    Magisk Modules

    Module packages, flashing through TWRP recommended, flashing through Magisk Manager possible starting with version 22.6.91 (22.7-beta2).

    • NanoDroid: includes
      • everything mentioned in the Summary
    • NanoDroid-microG: includes
      • microG and it's companions
      • GNU Bash
      • pseudo-debloat feature
      • app stores
    • NanoDroid-fdroid: includes
      • F-Droid and it's privileged extension
    • NanoDroid-BromiteWebView: includes
      • Bromite WebView
    • NanoDroid-OsmAnd: includes
      • OpenStreetMap for Android (OsmAnd+)

    Extras

    Extra packages, flashing through TWRP recommended, flashing through Magisk Manager possible starting with version 22.6.91 (22.7-beta2).

    • NanoDroid-pacher: includes
      • on-device framework-patcher (signature spoofing support)
    • NanoDroid-systest: includes
      • System Test script which generates a log to aid issue reporting
    • NanoDroid-uninstaller: includes
      • uninstalls all NanoMod/NanoDroid Magisk Modules
      • uninstalls NanoMod/NanoDroid installed in System Mode
      • uninstalls NanoMod/NanoDroid-Patcher addon.d environment

    The GitLab repository contains the full documentation with infos about

    • more detailed info what's included
    • detailed installation instructions
    • setup instructions for microG
    • list of known Issues (and fixes/workarounds)
    • more
    >> Full Documentation
    53
    I never had a look about how much users NanoDroid might have gotten meanwhile, but I checked the stats, just for fun. So, if you wanna know, I'm leaving this here.

    Just to make it clear: no personal information is stored, only basic stuff, like country of origin, Browser agent or what has been accessed, no tracking or profiling.

    All values from May 1st to May 24th, for HTTPS access only (HTTP access to my site is down to less than 5 %, so I didn't bother).

    NanoDroid (Zips):
    - Full/Stable: ~29.300 (!!)
    - Full/Beta: ~500
    - microG/Stable: ~16.500 (!!)
    - microG/Beta: ~1.000

    NanoDroid F-Droid repo:
    - F-Droid repo update checks: ~88.000
    - custom GmsCore installs: ~4.000
    - patched Play Store installs: ~3.500
    - unofficial MPV build installs: ~1.350

    Access by country (Zips):
    - unknown (unresolved, Tor, VPN, or unknown to statistic software): 52 %
    - Germany 5 %
    - Brazil 4 %

    Access by country (F-Droid):
    - unknown (unresolved, Tor, VPN, or unknown to statistic software): 30 %
    - Germany 11 %
    - Russia 4 %

    Top referers:
    - XDA
    - Miui Browser 'Hot'
    - 4PDA

    OMG, I'm working on a project which attracts more than 45.000 users (active users of course unknown). I never thought NanoDroid would become this huge.

    Thanks a lot for your ongoing support!
    42
    Hi everyone,

    I know I've been inactive for about 2 or 3 months here.

    Those who follow the git repository might already know that some groundbreaking work was going on since beginning of August.

    A new beta release 22.6.91 (= 22.7-beta2) will drop this weekend. What's to expect:

    - full support for Android 10 (many issues resolved)
    - full support for Android 10 **if deodexed** in the Patcher
    - flashing all Packages (except the Uninstaller, needs a few changes, still) through Magisk Manager, this includes the Patcher aswell (yes, yes!)
    - more. See ChangeLog.md for the full list.

    I won't go into reading the past 10+ pages, if there are any unresolved issues or questions, feel free to post them again (or in case of issues even better: create a ticket over at gitlab, with logs included).
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone