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

[ranton1990]

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.

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

 

[kurtn]

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

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

 

[ranton1990]

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

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?

 

[kurtn]

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?

Oops. Nanodroid installed some non-standard APP. And it's no longer part oft nanodroid repository. So you really should flash a nanodroid update.

 

[ranton1990]

Oops. Nanodroid installed some non-standard APP. And it's no longer part oft nanodroid repository. So you really should flash a nanodroid update.

Okay, i installed from zip with the same settings id did before, now everything seems to be allright. Thanks a lot guys

 

[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

 

[kurtn]

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

Patcher is not compatible with android 11, yet.

 

[citizenserious]

Patcher is not compatible with android 11, yet.

Many thanks for the quick reply. Oh, I was assuming the new version would support Android R, I got that wrong. Sorry for bothering.

 

[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.

 

[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?)

 

[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)

 

[Roberto W.]

still error while mounting /system on twrp

unsupported a/b device

while installing nanodroid google.zip

using magisk works fine

 

[rayman95]

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.

Flash latest beta NanoDroid-patcher-22.91.20201021...had same issue

 

[Setialpha]

still error while mounting /system on twrp

unsupported a/b device

while installing nanodroid google.zip

using magisk works fine

Actually, no. There's something complety wrong on your Samsung device trying to setup busybox, basically the whole installer fails. I'll investigate.

 

[K9100ii]

Actually, no. There's something complety wrong on your Samsung device trying to setup busybox, basically the whole installer fails. I'll investigate.

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.

 

[Setialpha]

The problem is that the following architecture check for which architecture busybox binary should be used (arm or x86) in the CommonInstaller script fails 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.

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".

 

[Setialpha]

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.

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

 

[K9100ii]

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

You're missing aarch64 (64-bit ARM). The binary for arm should be selected if it returns 'aarch64'.

 

[Setialpha]

You're missing aarch64 (64-bit ARM). The binary for arm should be selected if it returns 'aarch64'.

Yes, fixed, I completely missed that.

 

[Sc4r3Crow]

@Setialpha I'm using Nandroid since a couple of months and I love it

Some time ago I've realized that I can't save contacts to my device anymore, that means I can't select my device as standard account for new contacts. I only have the opportunity to use either a Google account or one of my email accounts for saving them.
Is that related to the latest build of NanoDroid/MicroG or to the custom rom I'm using?

I'm not 100% sure but I think when I was using an older build of NanDroid with the same rom I'm using atm, I've been able to save contacts to device directly