FORUMS

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

2,435 posts
Thanks Meter: 5,732
 
Post Reply Email Thread
11th May 2020, 06:08 PM |#7981  
Senior Member
Thanks Meter: 531
 
More
Quote:
Originally Posted by d1n0x

This "updating Play support libraries" notification is starting to get on my nerves. I disabled every possible service for Play Store imaginable without breaking it, I disabled it from running in the background, but I still get this annoying notification about play support libraries again and again and again. Can we please have a definitive answer on how to disable this, other than disabling the app completely?

This didn't work?

https://gitlab.com/Nanolx/NanoDroid/...port-libraries
11th May 2020, 07:57 PM |#7982  
Senior Member
Thanks Meter: 1,738
 
More
Quote:
Originally Posted by andy356

This didn't work?

https://gitlab.com/Nanolx/NanoDroid/...port-libraries

Of course. I disabled that service but it didn't stop, so I disabled others but I still get it frequently
11th May 2020, 08:27 PM |#7983  
Junior Member
Thanks Meter: 0
 
More
While doing clean install of rom, I tried to install nanodroid but no success, phone keeps rebooting in twrp. with opengapps everything works fine

Is there some specific procedure how to do it, step by step, or this rom ( crdroid) is maybe not supporting it ?
11th May 2020, 08:36 PM |#7984  
Senior Member
Thanks Meter: 1,738
 
More
Quote:
Originally Posted by Djurba

While doing clean install of rom, I tried to install nanodroid but no success, phone keeps rebooting in twrp. with opengapps everything works fine

Is there some specific procedure how to do it, step by step, or this rom ( crdroid) is maybe not supporting it ?

Boot into ROM once before flashing NanoDroid
The Following User Says Thank You to d1n0x For This Useful Post: [ View ] Gift d1n0x Ad-Free
11th May 2020, 08:48 PM |#7985  
Senior Member
Thanks Meter: 23
 
More
Hi @Setialpha! Hope you are doing well. Thank you for all of your hard work, it is very much appreciated. I've been using Nanodroid on my OP6T since late 2019 and it's my favorite open source installer.
I have been using Nanodroid 22.4 but over the weekend I decided I wanted to upgrade to the latest Nanodroid. I think it's 22.6. I ran into an issue. When I attempt to flash it in TWRP it says it is not a recognized zip file. I am on android 9 and I have magisk installed on a custom ROM with signature spoofing support. The ROM is android extended.

Thank you.
11th May 2020, 09:05 PM |#7986  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by d1n0x

Boot into ROM once before flashing NanoDroid

Its working now , thanks!!!

After booting to system do I need to set up something to complete MicroG setup ??

finally I found some instructions on GitLab, I am supposed to do this

https://imgur.com/9PVXfMJ
14th May 2020, 06:40 PM |#7987  
Senior Member
Thanks Meter: 23
 
More
Quote:
Originally Posted by TRexombo

Hi @Setialpha! Hope you are doing well. Thank you for all of your hard work, it is very much appreciated. I've been using Nanodroid on my OP6T since late 2019 and it's my favorite open source installer.
I have been using Nanodroid 22.4 but over the weekend I decided I wanted to upgrade to the latest Nanodroid. I think it's 22.6. I ran into an issue. When I attempt to flash it in TWRP it says it is not a recognized zip file. I am on android 9 and I have magisk installed on a custom ROM with signature spoofing support. The ROM is android extended.

Thank you.

Been thinking about this issue. Is it because I need to ADB side load it? My previous version (22.4) installs just fine in TWRP but 22.6 always gives me the invalid zip error.
I have the latest TWRP on my OP6T
Edit:
Or is it only compatible with Android 10?
21st May 2020, 04:41 PM |#7988  
Setialpha's Avatar
OP Senior Member
Flag NĂ¼rnberg
Thanks Meter: 5,732
 
Donate to Me
More
Quote:
Originally Posted by TRexombo

Been thinking about this issue. Is it because I need to ADB side load it? My previous version (22.4) installs just fine in TWRP but 22.6 always gives me the invalid zip error.
I have the latest TWRP on my OP6T
Edit:
Or is it only compatible with Android 10?

I would rather say that your downloaded zip is faulty. Try downloading it again.
The Following 2 Users Say Thank You to Setialpha For This Useful Post: [ View ] Gift Setialpha Ad-Free
24th May 2020, 01:51 AM |#7989  
Senior Member
Thanks Meter: 23
 
More
Quote:
Originally Posted by Setialpha

I would rather say that your downloaded zip is faulty. Try downloading it again.

Yes, thank you. You are exactly right! I re downloaded my zip and tried it again. Now it works
The Following User Says Thank You to TRexombo For This Useful Post: [ View ] Gift TRexombo Ad-Free
25th May 2020, 01:53 AM |#7990  
Junior Member
Thanks Meter: 3
 
More
I can not concur that the patcher works for Android 10 - at least not with all devices. I have a S10+ and the patcher fails with the following log:

Quote:

Iperation_start: 'Flashing'
Installing zip file '/sdcard/NanoDroid-patcher-22.6.90.20200418.zip'
Checking for Digest file...
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.
mkdir: can't create directory '/dev/tmp': File exists
ps: invalid option -- A
BusyBox v1.22.1 (2020-04-12 01:47 +0300) multi-call binary.

Usage: ps

Show list of processes

-Z Show selinux context
w Wide output
l Long output
T Show threads


********************************
NanoDroid
Framework Patcher
Powered by DexPatcher
22.6.90.99999999
********************************

INFO: #1 [SLOT]
INFO: #2 [SLOT]
INFO: #4 [system_tmp] /dev/block/by-name/system
INFO: #5 [SYSTEM_BLOCK] /dev/block/sda25
INFO: #6 [vendor_tmp] /dev/block/by-name/vendor
INFO: #7 [VENDOR_BLOCK] /dev/block/sda26
mount: mounting /dev/block/sda26 on /vendor failed: Device or resource busy

rootfs on / params: (rw,seclabel)
tmpfs on /dev params: (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts params: (rw,seclabel,relatime,mode=600,ptmxmode=000)
proc on /proc params: (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys params: (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux params: (rw,relatime)
tmpfs on /mnt params: (rw,seclabel,nosuid,nodev,noexec,relatime,mode=755 ,gid=1000)
none on /acct params: (rw,relatime,cpuacct)
tmpfs on /tmp params: (rw,seclabel,relatime)
none on /sys/kernel/config params: (rw,relatime)
adb on /dev/usb-ffs/adb params: (rw,relatime)
mtp on /dev/usb-ffs/mtp params: (rw,relatime)
pstore on /sys/fs/pstore params: (rw,seclabel,relatime)
/dev/block/sda28 on /cache params: (rw,seclabel,relatime,i_version,data=ordered)
/dev/block/sda31 on /data params: (rw,seclabel,relatime,resgid=5678,i_version,data=o rdered)
/dev/block/sda31 on /sdcard params: (rw,seclabel,relatime,resgid=5678,i_version,data=o rdered)
/dev/block/sda25 on /system_root params: (rw,seclabel,relatime,i_version)
/dev/block/sda26 on /vendor params: (rw,seclabel,relatime,i_version,data=ordered)
/dev/block/sda3 on /efs params: (rw,seclabel,relatime,i_version)
/dev/block/sda27 on /product params: (rw,seclabel,relatime,i_version,data=ordered)
tmpfs on /dev/random params: (rw,seclabel,nosuid,relatime,mode=755)
tmpfs on /dev/random params: (rw,seclabel,nosuid,relatime,mode=755)

INFO: #8 [prop]
-rw------- 1 root root 4564 Apr 16 05:16 /system/build.prop
INFO: #9 [build_props] /system_root/system/build.prop
/vendor/build.prop
/vendor/odm/etc/build.prop
INFO: #10 [APEX_NAME] com.android.runtime.release
INFO: #11 [APEX_FILE]
INFO: #12 [APEX_DIR] /system/apex/com.android.runtime.release
INFO: #13 [APEX_LD] /apex/com.android.runtime.release
ls: /system/apex/*.apex: No such file or directory
INFO: #14 [APEX [ALL]]
> preparing environment
> Android 7.0 - 10.0 (SDK 29) detected
__bionic_open_tzdata: couldn't find any tzdata when looking for CET-1CEST,M3.5.0,M10.5.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
> device architecture: arm64

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

> patching signature spoofing support

>> patching services.jar
/tmp/updater: line 48: /system/bin/dalvikvm: not found

!! failed to apply patches

Updater process ended with ERROR: 1
I:Install took 1 second(s).



Seems to me that the updater does not find dalvikvm because it does not receive the right path after all the traversal. But I am not sure.

I did a ls -l to that path and I see it a link to
lrwxrwxrwx 1 root root 38 2020-05-25 01:48 system/bin/dalvikvm -> /apex/com.android.runtime/bin/dalvikvm
and another link to
/apex/com.android.runtime/bin/dalvikvm -> dalvikvm64
This then gives something that is not a link, but has the owner shell for a change
-rwxr-xr-x 1 root shell 28552 2008-08-01 14:00 /apex/com.android.runtime/bin/dalvikvm64

I guess if the updater were to find this exact location, it would succeed. Maybe it helps at correcting the problem?
Yesterday, 09:08 AM |#7991  
Senior Member
Thanks Meter: 43
 
More
Hi, I hope everybody is fine and I want to thank as well Setialpha for all his important and hard work.
Unfortunately I have the same problem with the Patcher and Android 10 - updater process ended with ERROR:1
It's the Fairphone 2 of my daughter with LOS 17.1 and Magisk 20.4 and the Beta-Patcher. I found no log for the Patcher only for microG. Unfortunately the USB connection of Android devices with my PC is not seriously working so the option with Smali-Patcher does not work for me
Post Reply Subscribe to Thread

Tags
aosp, f-droid, lineageos, magisk, microg

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes