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

Search This thread

-Happy Feet-

Senior Member
Dec 19, 2008
1,690
253
Flieden/Hessen
dasnetzundich.de
Found signature spoof in App permissions. Checked it. Found Droid helper in Magisk Hide. Check it. Even flashed a fresh install. Clean as it can get on A/B partition. Same results. I can't flash setup wizard(reinstalled but, I'll try again) and this is MicroG check up results in the pic. However, everything else runs fine. Even the play store.

OnePlus 6t Int.

Have this problem also.
 

Setialpha

Senior Member
Jul 24, 2011
2,552
5,857
Nürnberg
www.nanolx.org
OnePlus 7T
Found signature spoof in App permissions. Checked it. Found Droid helper in Magisk Hide. Check it. Even flashed a fresh install. Clean as it can get on A/B partition. Same results. I can't flash setup wizard(reinstalled but, I'll try again) and this is MicroG check up results in the pic. However, everything else runs fine. Even the play store.

OnePlus 6t Int.

What ROM? I suppose you're using version 20.4 of NanoDroid?

For LineageOS this issue has been fixed with 20.4, but some other ROMs have an additional "master switch" in their own Settings which enables Signature Spoofing or not.
 
  • Like
Reactions: Koont

Setialpha

Senior Member
Jul 24, 2011
2,552
5,857
Nürnberg
www.nanolx.org
OnePlus 7T
I just tried installing the newest stable update (12/30) and got an error about being unable to install phonesky libs. I then tried to flash the previous version back and it's giving me an error about libs for gmscore_nanodroid failed. That version installed fine before. I can get the new version to install fine with fakestore&yalpstore but my paid apps don't play well with that setup. I also get an error about installing the libs for aororastore when trying it that way. Not sure what's going on. Which file in data/adb/ do i need to upload and where's the best place to upload it? I think all the files are too big to add as attachments and too big to use pastebin.

The installation logs are not too big to upload here, it's /data/adb/MODID_log_INSTALLDATE and /data/adb/MODID_twrp_INSTALLDATE, where MODID is the Package you've flashed and INSTALLDATE the time and date you installed it.

But: nothing changed in the installer compared to the previous version in that regard, so it should work just as before. Are you using the latest (official) version of TWRP for your device?
 

Koont

Senior Member
Aug 14, 2008
534
151
What ROM? I suppose you're using version 20.4 of NanoDroid?

For LineageOS this issue has been fixed with 20.4, but some other ROMs have an additional "master switch" in their own Settings which enables Signature Spoofing or not.
Havoc ROM for OnePlus 6t. And, your right I'm on 20.4. I'll search around. My bad. Been fondling my new phone since black Friday and hadn't been keeping up with development. Thanks
 

oF2pks

Senior Member
May 22, 2016
772
1,068
Hi @Setialpha , thx for advanced DroidGuardHelper & gmscore14.7.99 on repo : https://www.nanolx.org/fdroid/repo
Can you upload non-debug flavor: debug is not supposed to be battery friendly for "dynamic non static" apps (?).
For info, apks can be "null"-signed: void first 6x asking [What?] + 1 "y" for latest [Is?] for keytool... , and after zipalign 4...,you can use "android" as generic password with apksigner sign --ks debug.keystore *.apk
Code:
[SIZE="1"]$ keytool -genkey -v -keystore debug.keystore -storepass android -alias androiddebugkey -keypass android -keyalg RSA -keysize 2048 -validity 10000
What is your first and last name?
  [Unknown]:  
What is the name of your organizational unit?
  [Unknown]:  
What is the name of your organization?
  [Unknown]:  
What is the name of your City or Locality?
  [Unknown]:  
What is the name of your State or Province?
  [Unknown]:  
What is the two-letter country code for this unit?
  [Unknown]:  
Is CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
  [no]:  y

Generating 2,048 bit RSA key pair and self-signed certificate (SHA256withRSA) with a validity of 10,000 days
	for: CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown
[Storing debug.keystore]

Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore debug.keystore -destkeystore debug.keystore -deststoretype pkcs12".[/SIZE]

Also, do you change MAX_REFERENCE_VERSION in https://github.com/microg/android_e...bc04e0b#diff-064598cbf8b67520465b27cbc3c9f458 ? edit : indeed.
Finally , ( @ale5000 ) GoogleContactsSyncAdapter should be moved to privileged /priv-app, due to INTERACT_ACROSS_USERS privapp-permissions needed (?).

Reinstall version 9.83 from apkmirror and disable automatic updates for maps in play store.
For the record, latest compatible is 9.84.2 uploaded here https://androidfilehost.com/?fid=11410963190603886579
If it makes sense to some, I noticed (with apktool) that Maps9.84.2 includes a /com/google/android/apps/gmm/shared/net/v2/grpc/CAcert.pem (attached) , which appears in gmscore14.3.66 only /com/google/android/libraries/micore/learning/testing/grpctestchannel/CAcert.pem

btw , for users who don't want trackers, you can scan your apks (keyboard...) with ClassyShark3xodus/fdroid
 

Attachments

  • CAcert.pem.txt
    1.7 KB · Views: 5
Last edited:
  • Like
Reactions: TiTiB

masterxxxxxl

Senior Member
Mar 30, 2013
72
5
Aachen
the nanodroid setupwizard freezes my LG G7's TWRP. The last thing that gets printed out before is "(c) 2013 by amarullz xda-developers".
Are logs already generated at this point? Where do I get them?
 

Setialpha

Senior Member
Jul 24, 2011
2,552
5,857
Nürnberg
www.nanolx.org
OnePlus 7T
the nanodroid setupwizard freezes my LG G7's TWRP. The last thing that gets printed out before is "(c) 2013 by amarullz xda-developers".
Are logs already generated at this point? Where do I get them?

If it doesn't work, you'll need to generate the files manually. AROMA isn't supported by it's developer anymore.
 
Last edited:
  • Like
Reactions: masterxxxxxl

Setialpha

Senior Member
Jul 24, 2011
2,552
5,857
Nürnberg
www.nanolx.org
OnePlus 7T
Hi @Setialpha , thx for advanced DroidGuardHelper & gmscore14.7.99 on repo : https://www.nanolx.org/fdroid/repo
Can you upload non-debug flavor: debug is not supposed to be battery friendly for "dynamic non static" apps (?).
For info, apks can be "null"-signed: void first 6x asking [What?] + 1 "y" for latest [Is?] for keytool... , and after zipalign 4...,you can use "android" as generic password with apksigner sign --ks debug.keystore *.apk

Also, do you change MAX_REFERENCE_VERSION in https://github.com/microg/android_e...bc04e0b#diff-064598cbf8b67520465b27cbc3c9f458 ? edit : indeed.
Finally , ( @ale5000 ) GoogleContactsSyncAdapter should be moved to privileged /priv-app, due to INTERACT_ACROSS_USERS privapp-permissions needed (?).


For the record, latest compatible is 9.84.2 uploaded here https://androidfilehost.com/?fid=11410963190603886579
If it makes sense to some, I noticed (with apktool) that Maps9.84.2 includes a /com/google/android/apps/gmm/shared/net/v2/grpc/CAcert.pem (attached) , which appears in gmscore14.3.66 only /com/google/android/libraries/micore/learning/testing/grpctestchannel/CAcert.pem

btw , for users who don't want trackers, you can scan your apks (keyboard...) with ClassyShark3xodus/fdroid

The debug build is required for signature spoofing through Xposed. I'll have a look regarding Sync Adapters (don't use them personally).
 

AlreadyFree

Member
Feb 1, 2017
42
3
The installation logs are not too big to upload here, it's /data/adb/MODID_log_INSTALLDATE and /data/adb/MODID_twrp_INSTALLDATE, where MODID is the Package you've flashed and INSTALLDATE the time and date you installed it.

But: nothing changed in the installer compared to the previous version in that regard, so it should work just as before. Are you using the latest (official) version of TWRP for your device?

Ok. the 13.05 files are from my attempt to install the new version and the 13.09 files are from when I tried to reinstall the previous version. the last file is from the data/adb/logcat folder so assuming that's the logcat you're always asking for :) Just have to change the extensions back to .txt
 

Attachments

  • NanoDroid_log_20190101_13.05.tar
    1.2 KB · Views: 0
  • NanoDroid_twrp_20190101_13.05.tar
    3.4 MB · Views: 0
  • NanoDroid_log_20190101_13.09.tar
    1.2 KB · Views: 0
  • NanoDroid_twrp_20190101_13.09.tar
    3.4 MB · Views: 0
  • 20190101-04.47.tar
    9.1 MB · Views: 0

Shobit Joura

Senior Member
Jun 11, 2015
343
66
Hello devs i just flashed the patcher on vdex rom and then fter rebooting the rom sytem started lagging very much ....is there any fix?????


Its rr oreo 8.1.0
 

Setialpha

Senior Member
Jul 24, 2011
2,552
5,857
Nürnberg
www.nanolx.org
OnePlus 7T
I've looked into OxygenOS on OP+5T and it's not possible to fully fix it automatically.

Steps required:
- flash OOS
- optional: flash Magisk
- boot into ROM (if never booted into before)
- flash NanoDroid
- boot into ROM
- issue the following commands, as root, on-device to make NanoDroid/microG work with OOS:
Code:
pm install -r /system/priv-app/GsfProxy/GsfProxy.apk
pm install -r /system/priv-app/Phonesky/Phonesky.apk
pm install -r /system/priv-app/GmsCore/GmsCore.apk

Now everything works, including unified nlp.
 
Last edited:

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
    Hi all,

    what is the usual upgrade procedure for NanoDroid?
    I had installed NanoDroid 2 years ago on LineageOS (Android 9). Since then, F-Droid had always updated all my apps (including itself), so I never thought that any further maintenance was necessary.
    But now I noticed that my microg seems to be still ages old (gmscore 0.2.8.17785-beta-1 from summer 2019) while the current microg tag is 0.2.18.204714.

    To upgrade my microg,
    • should I reinstall a current NanoDroid package from TWRP?
    • or would it be more appropriate to just install a current microg from microg.org?
    • or is my F-Droid app just missing a repo configuration to handle microg updates automatically? F-Droid's current config includes {Nanolx F-Droid Repo, Bromite official F-Droid Repository, microg F-Droid repo, F-Droid} as pkg sources.
    • or better not upgrade and stick to what I have?
    I'll be thankful for any good advice.
    Don't know if my post here in the µG thread helps. I've updated via F-droid. Maybe check what repos are setup in F-droid.
  • 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