• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

Bracher

Senior Member
Sep 18, 2009
202
49
Thanks a lot it helped the phone restartet!!! And MicroG is installed, but I could not test it yet, I intend to get signature spoofing via FakeGApps, everything is proper installed (Riru, LSP, FakeGApps via whew inc installed and activated, but it could not be tested as my old SIM Card has the wrong format and I have to wait till the Nano SIM arrives, than I will check.
 
  • Like
Reactions: Roberto W.

Yoshi_523

Senior Member
Sep 11, 2010
137
68
Hi,
Incase anyone is wondering my conclusion after I beleive a successfull install of NanoDroid & microG is that apps that use Google Play Services for location/maps like Uber Taxi app & WeatherZone app don't work any more. They each display an error regarding the Google Play Services after installing microG. Google Maps does work but with a significant delay which looks like it's requiring a GPS lock before displaying any location at all as opposed to when using the real Google Play Services it gets a location immidiately by using phone tower based location and Wi-Fi assisted GPS in the interium until adqueite GPS signal is achieved.

I installed latest NanoDroid-microG-23.1.2.20210117.zip in TWRP on my Samsung Galaxy S4 (Stock, Rooted, Debloated & Deodexed ROM). I then installed the latest microG Sevices Core apk (com.google.android.gms-212158042.apk).

I think I will just restore my previous TWRP backup and forget about microG that is unless someone has any fix?

So far the old tried and tested way I've been using Google Maps, Uber and WeatherZone without a google account is by only installing an old version of Google Play Services (v12.8.74 from 20-Jul-2018) and and old version of Google Maps (v9.55.1 from 17-Jun-2017). I found these on APKmirror.com. I'm not sure if newer verions of Uber work or not but I've just stuck to using the old version (v4.240.10001 from 4-Dec-2018).
 

kurtn

Senior Member
Jan 28, 2017
4,238
1,839
Small town in Bavaria
Hi,
Incase anyone is wondering my conclusion after I beleive a successfull install of NanoDroid & microG is that apps that use Google Play Services for location/maps like Uber Taxi app & WeatherZone app don't work any more. They each display an error regarding the Google Play Services after installing microG. Google Maps does work but with a significant delay which looks like it's requiring a GPS lock before displaying any location at all as opposed to when using the real Google Play Services it gets a location immidiately by using phone tower based location and Wi-Fi assisted GPS in the interium until adqueite GPS signal is achieved.

I installed latest NanoDroid-microG-23.1.2.20210117.zip in TWRP on my Samsung Galaxy S4 (Stock, Rooted, Debloated & Deodexed ROM). I then installed the latest microG Sevices Core apk (com.google.android.gms-212158042.apk).

I think I will just restore my previous TWRP backup and forget about microG that is unless someone has any fix?

So far the old tried and tested way I've been using Google Maps, Uber and WeatherZone without a google account is by only installing an old version of Google Play Services (v12.8.74 from 20-Jul-2018) and and old version of Google Maps (v9.55.1 from 17-Jun-2017). I found these on APKmirror.com. I'm not sure if newer verions of Uber work or not but I've just stuck to using the old version (v4.240.10001 from 4-Dec-2018).
You don't write a word about signature spoofing. Can you check that in microg self-check?
 

Bracher

Senior Member
Sep 18, 2009
202
49
Unfortunately the method with RiruLSP and FakeGapps did not work for me. In case I did something wrong:
I have a fairphone 3 with a and b partition so I'm normally on LOS Recovery but can boot in twrp via bootloader
so my way:
fresh install of LOS (infact factory reset/wipe date in LOS recovery) and reboot, developperoptions USB Debugging,
Magisk - Busybox - Riru - Riru LSPosed activated (a bit strange was that LSP did not aks for root like EdXposed)
than I flashed Nanoroid microG via Magisk - stuck in boot
Rebooted in TWRP flashed Magisk Modul microG Installer revived
Rebooted sucessful. installed FakeGapps and activated it in LSP - reboot- dial *#*#CHECKIN#*#* reboot
But unfortunately this solved not my spoofing problem - no chanceto give spoofing allowance.
I would be very thankful if somebody could give me a hint
 

kurtn

Senior Member
Jan 28, 2017
4,238
1,839
Small town in Bavaria
Unfortunately the method with RiruLSP and FakeGapps did not work for me. In case I did something wrong:
I have a fairphone 3 with a and b partition so I'm normally on LOS Recovery but can boot in twrp via bootloader
so my way:
fresh install of LOS (infact factory reset/wipe date in LOS recovery) and reboot, developperoptions USB Debugging,
Magisk - Busybox - Riru - Riru LSPosed activated (a bit strange was that LSP did not aks for root like EdXposed)
than I flashed Nanoroid microG via Magisk - stuck in boot
Rebooted in TWRP flashed Magisk Modul microG Installer revived
Rebooted sucessful. installed FakeGapps and activated it in LSP - reboot- dial *#*#CHECKIN#*#* reboot
But unfortunately this solved not my spoofing problem - no chanceto give spoofing allowance.
I would be very thankful if somebody could give me a hint
Did you give spoofing permission in fakegapps? Can you show microG self-check?
 

Bracher

Senior Member
Sep 18, 2009
202
49
Did you give spoofing permission in fakegapps? Can you show microG self-check?
FakeGapps did not ask for any permission so how shoudl I give this permission and as for MicroG this is strange (it's German so I try to translate:
Box one: your system supports signature spoofing, but the box is not ticked and no app is asking for it and ther is no app Signature Spoofing Support.
The third boox issimilar Phonesky has the right signature but the box could not be ticked. all other boxes are ticked
No sorry the forthe box is similar to two
 

Bracher

Senior Member
Sep 18, 2009
202
49
Screenshot_20210812-203008_microG_Services_Core.png
 
Sep 3, 2017
5
1
Hello,
I experienced some issue while trying to install the patcher on LOS 18.1 from Magisk.
Here's the log :
Code:
- Copying zip to temp directory
- Installing NanoDroid-patcher-23.1.2.20210117.zip
 
********************************
 NanoDroid                     
 Framework Patcher             
 Powered by DexPatcher         
 23.1.2.20210117                     
********************************
 
 > preparing environment
 > Android 7.0 - 10.0 (SDK 30) detected
 *** LD_CONFIG_FILE=/apex/com.android.art/etc/ld.config.txt
 > device architecture: arm64
 > installation mode: MAGISK
 
  
 ++
 ++ services.jar status: DEODEX
 ++
 
 > patching signature spoofing support
 
 >> patching services.jar
 *** BOOTCLASSPATH=/apex/com.android.art/javalib/core-oj.jar:/apex/com.android.art/javalib/core-libart.jar:/apex/com.android.art/javalib/core-icu4j.jar:/apex/com.android.art/javalib/okhttp.jar:/apex/com.android.art/javalib/bouncycastle.jar:/apex/com.android.art/javalib/apache-xml.jar:/system/framework/framework.jar:/system/framework/ext.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/framework-atb-backward-compatibility.jar:/apex/com.android.conscrypt/javalib/conscrypt.jar:/apex/com.android.media/javalib/updatable-media.jar:/apex/com.android.mediaprovider/javalib/framework-mediaprovider.jar:/apex/com.android.os.statsd/javalib/framework-statsd.jar:/apex/com.android.permission/javalib/framework-permission.jar:/apex/com.android.sdkext/javalib/framework-sdkextensions.jar:/apex/com.android.wifi/javalib/framework-wifi.jar:/apex/com.android.tethering/javalib/framework-tethering.jar
 *** DALVIKVM_OPTS= -Xnoimage-dex2oat -verbose:class
Error preloading public library libandroid.so: dlopen failed: library "libstatssocket.so" not found: needed by /system/lib64/libandroid_runtime.so in namespace system
Aborted
 
 !! failed to apply patches
 
! Installation failed
Thanks for your help !
 

kurtn

Senior Member
Jan 28, 2017
4,238
1,839
Small town in Bavaria
Hello,
I experienced some issue while trying to install the patcher on LOS 18.1 from Magisk.
Here's the log :
Code:
- Copying zip to temp directory
- Installing NanoDroid-patcher-23.1.2.20210117.zip

********************************
NanoDroid                    
Framework Patcher            
Powered by DexPatcher        
23.1.2.20210117                    
********************************

> preparing environment
> Android 7.0 - 10.0 (SDK 30) detected
*** LD_CONFIG_FILE=/apex/com.android.art/etc/ld.config.txt
> device architecture: arm64
> installation mode: MAGISK

 
++
++ services.jar status: DEODEX
++

> patching signature spoofing support

>> patching services.jar
*** BOOTCLASSPATH=/apex/com.android.art/javalib/core-oj.jar:/apex/com.android.art/javalib/core-libart.jar:/apex/com.android.art/javalib/core-icu4j.jar:/apex/com.android.art/javalib/okhttp.jar:/apex/com.android.art/javalib/bouncycastle.jar:/apex/com.android.art/javalib/apache-xml.jar:/system/framework/framework.jar:/system/framework/ext.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/framework-atb-backward-compatibility.jar:/apex/com.android.conscrypt/javalib/conscrypt.jar:/apex/com.android.media/javalib/updatable-media.jar:/apex/com.android.mediaprovider/javalib/framework-mediaprovider.jar:/apex/com.android.os.statsd/javalib/framework-statsd.jar:/apex/com.android.permission/javalib/framework-permission.jar:/apex/com.android.sdkext/javalib/framework-sdkextensions.jar:/apex/com.android.wifi/javalib/framework-wifi.jar:/apex/com.android.tethering/javalib/framework-tethering.jar
*** DALVIKVM_OPTS= -Xnoimage-dex2oat -verbose:class
Error preloading public library libandroid.so: dlopen failed: library "libstatssocket.so" not found: needed by /system/lib64/libandroid_runtime.so in namespace system
Aborted

!! failed to apply patches

! Installation failed
Thanks for your help !
Patcher does not work on android 11. Use LSPosed fakegapps
 
Sep 3, 2017
5
1
Patcher does not work on android 11. Use LSPosed fakegapps
Thanks for tour reply.
I was questioning myself because on the gitlab, it is written :
Code:
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
So I hoped that it would be possible as my services.jar contains classes.dex.
 

wkn000

Senior Member
Jan 19, 2017
70
40
@bracker

Open LSPosed app (Should be Activated), go to Modules (x modules enabled), click FakeGapps, switch Module activated and then click Apps to use (MicroG GSM and GSF for example)
 
  • Like
Reactions: kurtn

jenslody

Senior Member
Jun 13, 2017
1,424
3,182
FakeGapps did not ask for any permission so how shoudl I give this permission and as for MicroG this is strange (it's German so I try to translate:
Box one: your system supports signature spoofing, but the box is not ticked and no app is asking for it and ther is no app Signature Spoofing Support.
The third boox issimilar Phonesky has the right signature but the box could not be ticked. all other boxes are ticked
No sorry the forthe box is similar to two
One stupid question, just to be sure:
did you try to tick the boxes directly, or did you tap on the text?
The first approach does not work.
 

Bracher

Senior Member
Sep 18, 2009
202
49
One stupid question, just to be sure:
did you try to tick the boxes directly, or did you tap on the text?
The first approach does not work.
both, but doesn't matter anymore, there is a new LOS-MicroG Version for FP3 I flashed this and in combination with a modified MicroG Installer from FriendlyNeighborhoodShane it worked perfectly. But thank you all very much for your help!!!
 

sb56637

Senior Member
Nov 29, 2010
172
12
Hi, a question about Android 11 ROMs and DroidPatcher: I understand that "Patcher does not work from TWRP". Is this just because Android 11 is always encrypted and TWRP can't access /data and /system ? Because I use the MoKee flavor of TWRP with MoKee, and it can access the encrypted data. The reason I don't want to use DroidPatcher through Magisk is because my device doesn't have A/B partitions and therefore Magisk would have to be re-installed after each update. Thanks for the help!
 

kurtn

Senior Member
Jan 28, 2017
4,238
1,839
Small town in Bavaria
Hi, a question about Android 11 ROMs and DroidPatcher: I understand that "Patcher does not work from TWRP". Is this just because Android 11 is always encrypted and TWRP can't access /data and /system ? Because I use the MoKee flavor of TWRP with MoKee, and it can access the encrypted data. The reason I don't want to use DroidPatcher through Magisk is because my device doesn't have A/B partitions and therefore Magisk would have to be re-installed after each update. Thanks for the help!
Patcher also fails on unencrypted android 11.
 
  • Like
Reactions: sb56637

zedoc

Senior Member
Dec 5, 2014
140
20
Hi, is it possible to flash LOS 18.1 MicroG version for my Lavender and flash Nanolx after that to bypass the Patcher problem on 11?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 351
    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).