yashsingh1/xdaforums huggingface dataset:
[Magisk] ssurell:
False detect Magisk

Have a S912 TV box running Nougat 7.1 and rooted with SuperSU and Xposed. Flashing NanoDroid-23.0.1.20201029.zip in TWRP recovery indicates Magisk mode, doesn't do anything to the system after rebooting. How can I force system mode?

(I had Magisk on on my system, removed using recovery uninstaller and changed to SuperSU)

I thought to edit CommonInstaller but not sure what line.

*Looks like I just need to create .nanodroid-setup file on internal storage containing

nanodroid_forcesystem=1
[Magisk] kurtn:
See the discussion above. You can force system installation with .nanodroid-setup
[Magisk] Oswald Boelcke:
In the most likely already existing .nanodroid-setup set nanodroid_forcesystem=1

Reference: https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/AlterInstallation.md#nanodroid_forcesystem

Afterwards flash Nanodroid.
[Magisk] ubuntiger:
Howto fix still missing Background Location and Receive SMS?

I have also seen this post, but don't really understand how it works and if it would still give some benefit after applying the latest updates (see below)

Hi [MENTION=4187311]Setialpha[/MENTION]

On my Mi8 LOS17.1 clean install with Magisk the microG Selftest fails for ACCESS_BACKGROUND_LOCATION and RECEIVE_SMS - at least I don't mangage to give those permissions, e.g. by tapping on them.

I first tried Flashing via TWRP, then via Magisk.

I ran

git pull
./build-package pull
./build-package all

before to have the latest NanoDroid and microG (GmsCore-v0.2.14.204215.apk).

Would you be so kind to check, fix if necessary, or let me know, what to do better?

Also I would be interested: How to fix manually?
[Magisk] kurtn:
Install that

https://download.lineage.microg.org/dipper/
[Magisk] daywalk3r666:
https://microg.org/fdroid/repo/com.google.android.gms-204215028.apk

install this and this fix your issue

for this permission microg must be an userapp

https://gitlab.com/harryhobo/NanoDroid/-/blob/master/doc/Issues.md#microg-lacks-features
[Magisk] oF2pks:
@Setialpha @Lanchon , for the record, both AndroidStudio AVD Api29 & 30 have services.dex (in /system/framework/services.jar) and accept https://github.com/shakalaca/MagiskOnEmulator (canary option).

Nanopatcher succeeds spoof signature fine on Api29, but replacing prebuilt GmsCore systemlessly with microG in /product, brings bootloop (probably due to automotive (?) aosp specifics in Api29). But sometime microG boots fine with https://github.com/Magisk-Modules-Repo/microG_installer , sometimes not (2x GmsCore in /system).

The good news is that AndroidStudio AVD Api30 boots fine with GmsCore replaced with microG (https://github.com/microg/GmsCore/files/5652857/microG_AVDx86api30_magiskMaRViN.zip), and latest Apktool 2.5.0 decompress services.dex right, but I have no idea how to patch /services/core/java/com/android/server/pm/PackageManagerService. straight.

fyi, phhusson has move his latest android11 Treble GSi with simplified microG signature spoofing : https://github.com/phhusson/platform_frameworks_base/commit/5f555b5a75f9dbe7391017bbfd5bc975b10cbdc4

I will build & test all-in-one microG android11 Treble GSI soon
[Magisk] Setialpha:
Long time no see, I've been busy with work and other stuff, I'll get back on here slowly the next weeks.
[Magisk] oF2pks:
I finally got android11 spoof working on AOSP11 AndroidStudio (+Magisk) via AVD, with working microG. @kurtn @daywalk3r666 @qane , if you have

adb pull /system/framework/services.jar (with classes.dex into but without classes3.dex) and know how to recover bootloops, check use of Linux java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex with latest https://github.com/DexPatcher/dexpatcher-tool/releases.

Once done, repack 4x classes_.dex in services.jar to a Magisk systemless module, with Setialpha org.spoofing.apk in /system/framework.

Caution:

core_ & hook_ were build straight from aosp11, not Lineage like previous ones: https://gitlab.com/oF2pks/haystack/-/commit/746d92faaf865cc39bad7ba25a3fb79fea8fed05

EDIT2: GPLv3 android11 gen sources: https://gitlab.com/oF2pks/haystack/-/tree/11-attempt

EDIT: sha256sum

b15402f43375bf2b04b5427be7475b3306d2df5f1b62cb6762b81d0a099f3f55 11core-services.jar.dex

b823d52df08979b278c758ea32d4e312797056cbaa21a3f4a1b45ff451c57937 11-hook-services.jar.dex
[Magisk] mugba:
thx, working flawlessly in xiaomi.eu :)
[Magisk] Novbidouille:
A big thank you, really happy to have been able to spoof my Redmi note 8 pro.

Just a little error in the file name in the command : 11core_services.jar.dex = 11core-services.jar.dex

For repack 4x classes_.dex in services.jar, I was missing this information :

zip -j services.jar classes*.dex

Thanks again.
[Magisk] Ivy123:
Hey guys,

Just moved from OnePlus 7 pro (Android 10 HavocOS) to OnePlus Nord (Android 11 CRDroid). Everything is working except Network Location??? Installed Dejavu and Mozilla and can't get them run. In the microg app I see my location when I click on Dejavu, but I can't get a fix in my maps app.

Any ideas?
[Magisk] kurtn:
I've seen one report: install the location backeds additionally as user apps. So they can demand necessary permissions
[Magisk] Ivy123:
I made a little research.

I just installed microg from f-droid, so it's not a system app. Maybe that's the issue?

Did nanodroid microg zip run format you guys? It didn't work for me on Android 11.
[Magisk] Ivy123:
Edit: double post
[Magisk] kurtn:
Since android 7 or so, android accepts only system apps as location providers. That's the main reason for using flashable zips instead of app installation method. Yes. Nanodroid microG works for me.
[Magisk] Ivy123:
Yes got it. I had this issue before, but forgot about it.

I tried to install microg.zip via recovery but this doesn't work for me, but if it's working for you, I guess it hast something to do with my phone.

Also tried to install via magisk, but it doesn't work too. I will looking for support in my device forum.

Thanks for your help.
[Magisk] Sc4r3Crow:
How did you install it?
[Magisk] Bracher:
Dear Setialpha, thank you do much for the last update (vers. 23.0.1) it solved my problem with location providers on LOS 17.1 perfectly well!!! Merry Christmas and Happy New Year
[Magisk] hashkross:
Hi there,

I'm new to Nanodroid and microG overall... I want to know what to do for the OTA survival setup? How to turn on OTA survival I have the .nanodroid-setup file ready will share mine too. Also is GNU Bash required? Same for busybox is it required? Also will the microG and components update themselves from fdroid if installed to system or via magisk module?

Also just a small request we would love to have a telegram group and channel for this microG and Nanodroid community. I zipped the .nanodroid-setup file as extension not allowed inside I have my required settings just please tell me solutions to above (admitted a lot) questions.
[Magisk] andy356:
@Setialpha Another ping. This app is very good now.
[Magisk] Setialpha:
I may have a look
[Magisk] hashkross:
How to get OTA survival for nanodroid full package and microG???
[Magisk] andy356:
@Setialpha There's this app on F-Droid that got an update very recently: Local GSM Location - A local cell tower based back (UnifiedNlp location provider (local GSM database)) - https://f-droid.org/packages/org.fitchfamily.android.gsmlocation

Should it be included? Deja Vu was last updated a year ago. I don't know if that matters.

Also, how about a point release for the Newpipe and SmartPack changes?

Lastly, thank you for removing XDA Labs.
[Magisk] kurtn:
There is no need to get an nanodroid update for each change in available back ends or apps. They have the same functionality, if installed or updated from f-droid.
[Magisk] andy356:
This app isn't present in NanoDroid right now. I'm offering it up for consideration for inclusion. This is a different app which might/might not have better functionality than the existing Deja Vu backend's mobile tower location.
[Magisk] kurtn:
Read the list of back ends in https://github.com/microg/UnifiedNlp/blob/master/README.md . Each has different privacy and precision properties. There is no "better functionality" that fit's all. Please feel free to install whatever you like from f-droid and enable it in microG settings.
[Magisk] IronSingh:
I read a little, tried to search but xda search is broken for me. .

I have a fresh install on LOS 18.1

only rooted magisk, installed busy box, and nanodroid full package.

I signed in and am trying to get google play store to work. There is no play store am I supposed to use Aurora Store signed in?

In micro G I enabled everything but I can't enable locations. When I click on location modules the app closes without error.

I tried to install dejavu and unified nlp from f droid but it shows installed.

Thanks for any help.
[Magisk] Jord Dan:
Despite the documentation stating the Nanodroid Patcher works on Android 11 as a Magisk module, I receive an error that versions above 10 are not supported when attempting to patch in signature spoofing. Is a snapshot build required for this functionality, or is there a different workaround?

I am using Lineage 18.1, Magisk 21.1 with Manager 8.0.3, and Nanodroid-patcher 23.0.1.20201029. I have not manually deodexed my ROM, as the readme states this can be skipped if services.jar contains the file classes.dex.
[Magisk] 2faraway2:
Does your rom supports signature spoofing ?

If not (very likely), it could become a hard way to manage that because the nanodroid patcher imho didn't support android versions > 10 until now ..

If your rom supports signature spoofing (imho there isn't any LOS 4 MicroG 18.1 available), what does the microg self check screen look like ?
[Magisk] Jord Dan:
I have since built a snapshot Framework Patcher and attempted to flash it via Magisk. However, I received the following error:

Error preloading public library libandroid.so: dlopen failed: library "libstatssocket.so" not found: needed by /system/lib64/libandroid_runtime.so in namespace system
Aborted

How can this be fixed? I have attached the relevant Magisk log and can provide further information if needed.
[Magisk] oF2pks:
Check https://gitlab.com/Nanolx/NanoDroid/-/issues/169#note_471239114

and post https://xdaforums.com/t/module-syst...do-debloat-f-droid-apps.3584928/post-84088919
[Magisk] Setialpha:
For all custom build in NanoDroid (GNU Bash, MPV, SQLite 3*, Play Store*), I've setup a new git repository as central starting point to check what's up or to create your own builds:

Christopher Roy Bratusek / NanoDroid Patches · GitLab

NanoDroid patches (GNU Bash, MPV-Android)

gitlab.com

* just linked, reside in their own repos, for reasons

Feel free to have a look.
[Magisk] Marcyvee:
I know that is a stupid question.... Anyway, is there a way to use Google discover without play services?
[Magisk] EveryCoolNameWasTaken:
Hi.

I installed NanoDroid latest stable version as a Magisk module (by what I understood, doing this is auto mounts the installed apps as system apps) with default settings.

Is there an easy way for me to remove some apps, or do I need to edit the installer and do it again (actually, can I run the installer again through Magisk or will I screw everything up?).
[Magisk] citizenserious:
This is awesome work, is it possible to make it a flashable zip for noobs like me?

I would even try what you did, but I would need more detailed instructions :O

I know noobs like me are a pain in the ass but anyway I try asking. It would be epic if spoofing would work on lineage 18.1.
[Magisk] Setialpha:
You can simply adjust the setup, flash again (throgh MM) and reboot.
[Magisk] Draygon:
Is it possible to flash the Patched Playstore version to a locked bootloader OS (Like GrapheneOS or CalyxOS)?

This would be awesome, really would like to use it with the integrated MicroG of CalyxOS.
[Magisk] carlos974:
Thanks to @Setialpha for update (y)

Nanolx.org Downloads Archive
[Magisk] Setialpha:
You still need some way of installing something to /system directly, so if you have TWRP installed or did install Magisk before the bootloader was re-locked (if it was re-locked), it should be possible.

If you have root access to the device at all, you can also install it manually to /system like described here:

Christopher Roy Bratusek / microG-Phonesky-iap-support · GitLab

microG (in-)app-purchases support patches for Phonesky (Google Play).

gitlab.com
[Magisk] Setialpha:
Hi all,

NanoDroid 23.1 Codename Ni'Var is now available. This release includes many internal improvements, aswell as several bugfixes. Not all issues in regards of device compatibility have yet been resolved.

I do now have a secondary device again so more intense Android 11 testing will be forthcoming.

Full ChangeLog since version 23.0.1:

NOTE: There's now a git repository as central place/navigational point for all custom builds from NanoDroid:

* https://gitlab.com/Nanolx/nanodroid-patches

## Bug Fixes

* Installer, Addon
* read configuration files from `/system/addon.d` (fallback if TWRP can't mount `/data`)
* read configuration files from `/tmp` (fallback if TWRP can't mount `/data`)

* Uninstaller
* make use of bundled `busybox` at all

* CommonInstaller, Uninstaller, SysTest, Patcher
* setup bundled `busybox` before mounting partitions
* should fix segmentation faults reported on Sammy devices

* Full, microG packages
* fix that (in Magisk Mode) GmsCore was not automatically ensured to be a user app

## General Changes

* CommonInstaller
* resturctured, consolidated and cleaned-up code

* Addon
* simplify addon.d and remove unused functions

* NanoDroid-Overlay
* read configuration files from `/system/addon.d` (fallback if TWRP can't mount `/data`)
* read configuration files from `/tmp` (fallback if TWRP can't mount `/data`)

* NanoDroid-Util
* add `-R`, `--reset-permissions` switch

* Full package
* move from `Blokada` v4 to v5
* no longer ship `XDA Labs`
* grab `NewPipe` from NewPipe repo instead of F-Droid
* F-Droid build is outdated
* grab `SmartPack Kernel Manager` from F-Droid instead of Github

* Full, microG package
* add `android.permission.RECEIVE_SMS` to default granted microG permissions @Vavun
* merge sysconfig changes for Android 11 from experimental OpenGApps

* Full, F-Droid package
* add `NewPipe` repo to F-Droid's `additional_repos.xml` @Vavun

* Documentation
* re-structure and update Issues section
* minor updates

### Updates

* automatic
* microG GmsCore (0.2.16.204713)
* Amaze (3.5.2)
* Blokada (5.6.0)
* Bromite System WebView (87.0.4280.131)
* F-Droid (1.11)
* FreeOTP+ (2.2.13)
* KeePassDX (2.9.8)
* NewPipe (0.20.8)
* Open Camera (1.48.3)
* OpenLauncher (0.7.4)
* OSM Android (3.8.5)
* Privacy Browser (3.6.1)
* QKSMS (3.9.0)
* Simple Calendar (6.11.3)
* Simple Gallery (6.18.1)
* SmartPack-KernelManager (15.4)
* Termux (0.104)
* Tor Browser (10.0.07)
* Twidere (4.1.6)

* manual
* GNU Bash (5.1.0[4]-2 w/ Debian patches)
* SQLite3 (3.34.0
* MPV (20210104-nightly)

Download links

Download from Nanolx.

In case of errors, please provide

when installing from TWRP

/data/media/0/nanodroid_logs/MODID_log_INSTALLDATE

/data/media/0/nanodroid_logs/MODID_twrp_INSTALLDATE

/tmp/recovery.log

when installing from Magisk Manager

/data/media/0/nanodroid_logs/MODID_log_INSTALLDATE

press the save icon and post the Magisk Manager created logfile aswell

SysTest package logfile

logcat (if applicable)
[Magisk] ranton1990:
I am using Nanodroid in Magisk mode. As i understand from the readme, i have to reflash the newest zip to upgrade nanodroid. Do i have to reedit the .nanodroid-setup file to match my liking? Or does the upgrade somehow recognize my last settings? Thanks a lot!
[Magisk] kurtn:
If your current installation works satisfying and you only whish to update the installed apps, I propose, to not flash nanodroid, but update with f-droid.
[Magisk] ranton1990:
I especially look to update microG, but the fdroid repo wont let me due to wrong signature. Is there a certain fdroid repo? Or do i have to disable signature spoofing before updating microg through fdroid? Thanks
[Magisk] kurtn:
There is a microG repo. Maybe you should disable all other repos temporarily for f-droid to find the correct com.google.android.gms

F-Droid repository - microG Project
[Magisk] ranton1990:
Yes i tried that, but it wont let me due to "This app has been signed with a different key". When i try to enable unsupported versions in fdroid, it tells me to uninstall the app first. Could it be because in my case the 23.0.1. installer did not install microg as an user app?
[Magisk] kurtn:
Oops. Nanodroid installed some non-standard APP. And it's no longer part oft nanodroid repository. So you really should flash a nanodroid update.
[Magisk] ranton1990:
Okay, i installed from zip with the same settings id did before, now everything seems to be allright. Thanks a lot guys
[Magisk] citizenserious:
I tried to install the latest patcher on LOS 18.1 (Android 11) today getting this error:

- Copying zip to temp directory
- Installing NanoDroid-patcher-23.1.20210109.zip

********************************
NanoDroid
Framework Patcher
Powered by DexPatcher
23.1.20210109
********************************

chmod: /busybox.x86: No such file or directory
mkdir: can't create directory '/busybox': Read-only file system
ln: /busybox/busybox: No such file or directory
update-binary: line 333: /busybox.x86: not found
> 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=
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

Can someone help me please? Did I miss something? Same thing happens with busybox installed, just without the missing busybox part.

Thanks a lot :)
[Magisk] kurtn:
Patcher is not compatible with android 11, yet.
[Magisk] citizenserious:
Many thanks for the quick reply. Oh, I was assuming the new version would support Android R, I got that wrong. Sorry for bothering.
[Magisk] starbright_:
Applying latest stable patcher 23.1 to a LIneageOS17.1 (Magisk installed) device returns an error:

"Failed to mount /system (unsupported A/B device?)

What exactly can I do? I repeated the test with mounted system, but result keeps same.
[Magisk] starbright_:
I add the log for the failed patcher:

Installing zip file '/sdcard1/Install/NanoDroid-patcher-23.1.20210109.zip'
Checking for Digest file...
Unmounting System...
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.

********************************
NanoDroid
Framework Patcher
Powered by DexPatcher
23.1.20210109
********************************

chmod: /busybox.arm: No such file or directory
/tmp/updater[21]: /busybox.arm: not found
/tmp/updater[22]: sed: not found
INFO: #1 [SLOT]
/tmp/updater[22]: sed: not found
INFO: #2 [SLOT]
/tmp/updater[22]: readlink: not found
/tmp/updater[22]: mount: not found
failed to mount /data!
/tmp/updater[22]: mount: not found
/tmp/updater[22]: find: not found
/tmp/updater[22]: head: not found
/tmp/updater[22]: find: not found
/tmp/updater[22]: head: not found
/tmp/updater[22]: awk: not found
...
/tmp/updater[22]: awk: not found
/tmp/updater[22]: readlink: not found
INFO: #5 [SYSTEM_BLOCK]
/tmp/updater[22]: mkdir: not found
/tmp/updater[22]: mount: not found
/tmp/updater[22]: find: not found
/tmp/updater[22]: head: not found
/tmp/updater[22]: find: not found
/tmp/updater[22]: head: not found
/tmp/updater[22]: awk: not found
...
/tmp/updater[22]: awk: not found
/tmp/updater[22]: readlink: not found
INFO: #7 [VENDOR_BLOCK]
/tmp/updater[22]: readlink: not found
/tmp/updater[22]: mount: not found
/tmp/updater[22]: readlink: not found
/tmp/updater[22]: mount: not found
/tmp/updater[22]: readlink: not found

/tmp/updater[22]: mount: not found
/tmp/updater[22]: sed: not found
/tmp/updater[22]: awk: not found

INFO: #8 [prop]
/tmp/updater[22]: ls: not found

!! failed to mount /system (unsupported A/B device?)
[Magisk] Setialpha:
Hi everyone,

a new bugfix release 23.1.1, Codname Zora is now availabe!

ChangeLog

## 23.1.1.20210116 "[Zora](https://memory-alpha.fandom.com/wiki/Zora_(artificial_intelligence))"

## Bug Fixes

* Installer, Uninstaller, SysTest, Patcher
* fix bugs regarding mounting `/system` from TWRP

* Patcher
* fix a regression causing Patcher not to be properly executed

## General Changes

* Installer, Uninstaller, SysTest, Patcher
* improve mounting code `/system` from TWRP

* NanoDroid-Overlay
* check whether configuration file exists before doing anything (`-x`/`--create`)

## Updates

* automatic
* microG GmsCore (0.2.17.204714)
* Amaze (3.5.3)
* K-9 Mail (5.726)
* Simple Calendar (6.11.4)
* Tor Brower (10.0.8)

Download links

Download from Nanolx.

Bug Reporting

In case of errors, please provide

when installing from TWRP

/data/media/0/nanodroid_logs/MODID_log_INSTALLDATE

/data/media/0/nanodroid_logs/MODID_twrp_INSTALLDATE

/tmp/recovery.log

when installing from Magisk Manager

/data/media/0/nanodroid_logs/MODID_log_INSTALLDATE

press the save icon and post the Magisk Manager created logfile aswell

SysTest package logfile

logcat (if applicable)
[Magisk] Roberto W.:
still error while mounting /system on twrp

unsupported a/b device

while installing nanodroid google.zip

using magisk works fine
[Magisk] rayman95:
Flash latest beta NanoDroid-patcher-22.91.20201021...had same issue
[Magisk] Setialpha:
Actually, no. There's something complety wrong on your Samsung device trying to setup busybox, basically the whole installer fails. I'll investigate.
[Magisk] K9100ii:
The problem is that the following architecture check for which architecture busybox binary should be used (arm or x86) in the CommonInstaller script doesn't work on TWRP builds which use busybox (I got this check from the MicroG package):

setup_busybox () {
if [[ "$(uname -m)" == a* ]]; then
local bb_arch=arm
else local bb_arch=x86
fi
[...]

When this architecture check fails, the x86 busybox binary will be used instead, which will of course not execute on devices with an ARM CPU, and causes such issues.

You need to use a TWRP build which uses toolbox instead of busybox. This has absolutely nothing to do with who manufactured your device. I tested my own build of TWRP on my Galaxy Tab A 10.1" 2016, which uses toolbox instead of busybox, and the latest nanodroid packages (I tested the MicroG and Bromite webview packages) install perfectly fine.
[Magisk] Setialpha:
I figured that out meanwhile, I'll change the checks so they work with both toolbox and busybox. I didn't know TWRP comes with different "flavours".
[Magisk] Setialpha:
setup_busybox () fix compat with TWRP that uses busybox instead of toolbox (a05fdf8e) · Commits · Christopher Roy Bratusek / NanoDroid · GitLab

microG, F-Droid, GNU Bash, FOSS applications and more for Android

gitlab.com