yashsingh1/xdaforums huggingface dataset:
[Magisk] ithilion:
An F-Droid version bump from alpha would be nice. I don't know, if it's just me, but F-Droid couldn't read the repository. I had to download the current one and install it from the terminal.
[Magisk] guest4711:
No problems with microG f-droid repo and f-droid 1.1.alpha0 here.
[Magisk] ithilion:
Ok, thanks. Then I don't know what that was.
[Magisk] Setialpha:
NanoMod gitlab repositoy was removed, now using NanoDroid repository.

https://gitlab.com/Nanolx/NanoDroid

Why? NanoMod originally contained copies of all apks included, since git is bad at handling binaries the repository swell to no less than 2 GB, making it practically useless.

Since around version 9 or 10 NanoMod didn't contain the apks anymore (in the git repository), except self built ones like the modified PlayStore, but the git history already existed. The new cleaned-up NanoDroid repository is now only less than 18 MB.

[MENTION=7126506]Shadow53[/MENTION] find the new link for my PlayStore apk here: https://nanolx.org/apk/Phonesky.apk

IF there's demand I may re-upload the old repository for whatever purposes (I still have local copies), though I doubt why anyone would need it.
[Magisk] guest4711:
I like this name, it reminds me on Drau river... :)
[Magisk] Setialpha:
lol, Typo, fixed. Of course it's NanoDroid, not NanoDroud.
[Magisk] Shadow53:
Thanks for the heads up.
[Magisk] bagajohny:
Shouldn't typo such words:laugh:

---------- Post added at 04:44 AM ---------- Previous post was at 04:39 AM ----------

Any way to deodex odexed ROM without using Android studio? I found one method with titanium backup but it didn't work with DU Oreo ROM. And I need safetynet so no xposed.
[Magisk] blazzer12:
Documentation says name configuration file `.nanodroid-setup` but only `.nanomod-setup` in `/data` works.

Even then the file `.nanodroid-setup` in `/data` is getting appended with additional parameters after flashing and the configuration is not working as expected.

EDIT:

Disregard documentation when it says `nanodroid`, use `nanomod` everywhere.
[Magisk] Setialpha:
See just a few posts back, the project is renamed from NanoMod to NanoDroid. If you use NanoMod, the configuration file needs the nanomod name, the first NanoDroid release will be tomorrow, that will auto-migrate the old configuration files and will expect the nanodroid file name for them.
[Magisk] blazzer12:
I have been wracking my brain for hours. I even compared checksums of `NanoMod-15.1.1.20180120` in OP and the new git readme file. Anyway if anyone else has this issue see the edit on my previous comment.

---------- Post added at 04:10 AM ---------- Previous post was at 03:47 AM ----------

I have finally managed to install. I can login to Play Store and install apps but google account is not syncing. The contacts are not syncing. Does anyone have this problem? I did enable `gsync` parameter in the config file.
[Magisk] blazzer12:
Will google contacts sync?
[Magisk] Setialpha:
Did you grant all permissions to the sync adapters? It works for people (I don't use them myself), no other complaints since ages (if we disregard the installation bug).
[Magisk] juniorjpdj:
If you rename project, please also fix links in description...
[Magisk] abacate123:
Hello [MENTION=4187311]Setialpha[/MENTION], I dunno if you're aware of this already, but I've just flashed my rom, with the latest beta, and there's no ContactsSync app there so I can't sync my contacts, even though it was checked to install on the aroma installer. Weird.
[Magisk] Setialpha:
Please post the logs (/data/adb/.recovery_MODID + /data/adb/nanodroid_MODID).
[Magisk] rascalifah:
---delete---
[Magisk] kurtn:
NanoDroid patcher tested in Nougat and Oreo LineageOS. Clean install and dirty update survival are OK. Thanks.
[Magisk] Bracher:
Nanodroid Beta works well on my Samsung P9005 with a dirty flash of the newest nightly LOS 14.1 (plus Magisk 15.3) and after reboot in revovery flashing Nadodroid microG and Patcher, thank you very much
[Magisk] abacate123:
Sure, I forgot sorry.
[Magisk] Setialpha:
Thanks, found the issue, will provide a new build later today.
[Magisk] Setialpha:
I've re-uploaded the Full, microG and F-Droid 16.0~beta1 packages (labelled 16.0~beta1.1), with fixed system environment detection (architecture, SDK, ...). This should fix most (if not all) installation issues.
[Magisk] Bharadwaz:
https://shadow53.com/android/downloads/google-sync-adapters/

could i flash this for Google contact's sync
[Magisk] Setialpha:
Yes, but why? NanoDroid includes them, too. Use 16.1~beta1 and setup to install Sync Adapters. Also shadow53's stuff is not systemless.
[Magisk] Bharadwaz:
i think nanodroid contains Google play services instead of micro G
[Magisk] Setialpha:
lolwut? Of course NOT!
[Magisk] Bharadwaz:
so u r saying that it contains microg and sync features ???
[Magisk] evilvoice:
[MENTION=4187311]Setialpha[/MENTION] so what version of play store is the latest working? I ask because every update, you post a disclaimer saying that the newest doesn't work

---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------

Where do you get that idea? Did you not read the original post?
[Magisk] Setialpha:
microG with optional Google Sync Adapters. Read the documentation for all information.

shadow53's zip contains the same Adapters.

The version provided is the latest working with in app purchases. But you could use any official one from other sources, if you don't need to do new purchases. As soon as apktool is updated to support the newer version, I'll update my modified version.
[Magisk] guest4711:
Thanks, [MENTION=4187311]Setialpha[/MENTION] for your hard work.

I tried to clean an installation, but the latest beta-uninstaller gave me

/tmp/updater: line 191: syntax error: unexpected "elif" (expecting "then")

I tried this because the installation of the last beta went wrong on my jactivelte: Magisk was not detected. I'll wipe system and start over...

Edit: Missing "; then" at the end of line 188 ...
[Magisk] guest4711:
Installation of the last beta (...-microG) does not detect magisk. Tried two ways;

1. Wipe system, cache dalvik. Install Rom, magisk, nanodroid-microg. Reboot.

2. Wipe system, cache dalvik. Install Rom, magisk, Reboot. Install nanodroid-microg. Reboot.

Nothing worked. Logfiles for 2. try attached.
[Magisk] dugi9991:
I've managed to install the latest microG beta with the latest Magisk without any problems. OP3 and NitrogenOS ROM if that means anything.

I did a clean install - wiped everything the installed ROM, Magisk, Beta MicroG.
[Magisk] guest4711:
Uninstaller works after adding "; then" to the end of line 188 ... :good:

But installation of NanoDroid-microG-16.0_beta1.1.20180126.zip does not find magisk (installs to system). This problem occurs on jactivelte (see logs above). On jfltexx everything ok with same version of magisk.

Now testing installation of NanoMod-microG-15.1.20180119.zip -> installs fine (systemless).
[Magisk] DodoGTA:
Can you run

find /data -iname magisk 2>&1 1>/sdcard/findmagisk_jactivelte.txt

while in TWRP and pull and attach that generated file?
[Magisk] guest4711:
Here you are (quick and dirty)
[Magisk] Bracher:
Thanks a lot!!! For me the beta version (microG and patcher) works well after a dirty flash of newest LOS Nightly (v. 14.1) and Magisk 15.3 on both of my devices the Samsung Note 3 and the tablet SM-P605. But I had to reboot in recovery after flashing LOS and Magisk and could than flash the beta version in TRWP via MagiskManager successfully
[Magisk] guest4711:
Thank you. Working again. (Did an uninstall via TWRP to clean any traces of installation to /system, copied .nanodroid-setup from backup and flashed beta2.) :good:

Edit: Tested on other devices, too. Flashing via TWRP without problems, from magisk manager no success (simply returned after expanding zip to temp).
[Magisk] Setialpha:
I'll have a look for Magisk Manager installation during the next days.
[Magisk] kingsven149:
Support for Android 8.1?
[Magisk] dugi9991:
It works on Nitrogen OS, OP3, which is 8.1, so I'd say yes to that :)

I only flashed the microG file.
[Magisk] abacate123:
It literally says that it supports 8.1/sdk 27 (oreo) on the OP... lol
[Magisk] kingsven149:
No only official support for Android 8.0/sdk 26 on the OP...
[Magisk] guest4711:
NanoMod officially supports the following Android versions:
...
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)

See [MODULE/SYSTEM] NanoDroid 15.1/16.0~beta2 (microG, pseudo-debloat, F-Droid + apps) - https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/post71739848
[Magisk] abacate123:
Sorry, but are you blind? It's written there fellow.
[Magisk] kingsven149:
Sorry for me there were only support for Android 8.0. But now I load it new and there it is.
[Magisk] Setialpha:
The last commit's description, for your information:

* fix installation through Magisk Manager
* fix creating system overlays when installing through Magisk Manager
* fixed the most A-N-C-I-E-N-T NanoDroid bug (TMANB™)
* fix installation through Magisk Manager does not reach end properly
* code revision

Release soon-ish™
[Magisk] Ex_FallenSkyTear:
installed microG-nanoDroid 16.0 beta 2 on android 8.1, in systemless and play store give me "RH-01" error...
[Magisk] Setialpha:
Everything setup, including permissions? Log?
[Magisk] Ex_FallenSkyTear:
maybe everything is right.

you want logcat?
[Magisk] dugi9991:
When I receive that, I usually clean the GP cache and data, give the permission again to GP and then everything is fine.
[Magisk] Ex_FallenSkyTear:
yes, i've tried, don't work.
[Magisk] dugi9991:
Hm, weird :(

Maybe it's something related to GP?

I have another issue - my paid apps are not recognized when I search for them - they are showed as payable.

But, if I find them via the Library in My apps & games, I can install them from there.

Has anybody occurred this problem or is it just me? Also, if this is the inapproirate thread, I'll post in the microG thread.

Cheers!

EDIT: using the latest beta NanoDroid version, details of phone/ROM in signature. Everything setup and installed fine, permissions fine.
[Magisk] Ex_FallenSkyTear:
it randomly fix after few hours...
[Magisk] Setialpha:
No, haven't heard about that issue... logcat?
[Magisk] dugi9991:
This is caught in the log while I open GP and go to my apps and swap between 'Updates' and 'Installed'.

Let me know of something else is needed.

Cheers!

EDIT: just to add, on Nougat and previous beta version (last NanoMod), everything was fine.
[Magisk] Setialpha:
I'll check. Just to be sure: did you block the DailyHygieneService after it ran atleast once? If not, or you're unsure, unblock it for a few minutes and start and use Play Store during that time. If it then works properly (or even if not) block the service again.

I'm gonna soon test how things work out, if I spoof Play Store to a higher version number to avoid having to block the DailyHygieneService, or less often.
[Magisk] dugi9991:
You are the MAN!

Yeah, it could be me that I've blocked it to early.

Now I've unblocked it, re-ran the PS, all is fine.

I've blocked it again and try to test it a few times.

Thanks once again, will buy you a beer:highfive:

Cheers mate!
[Magisk] Setialpha:
Very good news! Play Store 8.8.12 can be properly edited using apktool, again!
[Magisk] dugi9991:
We who are on the latest beta can now just install the latest 16.0 version without hesitation?
[Magisk] Setialpha:
yes.
[Magisk] HaoZeke:
Thanks so much for the new mirror, great work as always!
[Magisk] guest4711:
Thank you, installing via Magisk Manager works fine, too.
[Magisk] abacate123:
Thanks buddy. Projects like these makes me enter xda everyday to check out what's new and test out things, keep up the great work :)
[Magisk] DodoGTA:
Why don't you use Bucket (formerly known as LibreSubstratum) instead of Substratum?
[Magisk] hungvip2001:
Hi guys. Very happy with new update.

Fixed the auto update loop of Google Play?
[Magisk] abacate123:
I guess it could be added and shown as an alternative app, instead changing it and put in the place of the original app, since bucket still in development and is pretty much simple in comparison with the substratum, imho it would be more fair this way (since I do use substratum myself).

- -

Yeah, at least for me here.
[Magisk] Setialpha:
LibreSubstratum only supports Nougat officially.
[Magisk] Keule-Tm:
Nougat with OMS, AFAIK. Quite rare.
[Magisk] dirtyreturn:
Hi XDA, I'm just curious, is there any way to support odex ROMs?
[Magisk] kurtn:
Yes. Use xposed fakekgapps instead of nanoDroid patcher
[Magisk] abacate123:
Uh, not that rare though, almost every custom rom on nougat, except LineageOS, has oms support officially added by its developers, so, it's pretty easy to find :P
[Magisk] h4waii:
For some strange reason, sigspoof UI isn't being enabled on one of my builds of LineageOS-14.1 with 16.0~beta2.

It's patched in to the framework correctly and runs fine, but no toggle is visible under "Developer Options" even though the sigspoof_ui value is set to 1. The config file is ready correctly, as all the other values are used.
[Magisk] Setialpha:
As mentioned in the documentation the patch is not applied on SDK 25 kr newer, as it does not work. Regardless of user's choice.
[Magisk] totalcmdext:
In the TWRP always return:

Updater process ended with ERROR: 1

when it is trying to execute dexpatcher.
[Magisk] Setialpha:
Did you atleast boit once in the ROM? recovery.log?
[Magisk] totalcmdext:
I have done the following steps

1. Flash ROM

2. Boot to ROM

3. Flash from recovery the NanoMod_MicroG

3. Boot to ROM

4. Flash from recovery the NanoMod_Patcher

Attached you could find the recovery log
[Magisk] Setialpha:
Thanks, will have a look at a fix later. Seems like a general problem with pre-Nougat ROMs (patcher says 4.1-6.0 detected). What version of android is it exactly?
[Magisk] Oswald Boelcke:
Is your ROM coming with Magisk? Unless it is you might want to flash Magisk v12 immediately after having flashed your ROM, and to install the Magisk Control apk after the reboot into system.
[Magisk] gh0st85:
Recovery.log

Installing zip file '/sdcard/TWRP/NanoMod-patcher-7.1.20170501.zip'

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

I:Zip does not contain SELinux file_contexts file in its root.

I:Legacy property environment initialized.

********************************

NanoMod 7.1.20170501

created by [MENTION=7925618]nanol[/MENTION]x

Framework Patcher

Powered by DexPatcher (@lanchon)

********************************

> Android 7.x detected

> preparing environment

Archive: /sdcard/TWRP/NanoMod-patcher-7.1.20170501.zip

creating: dexpatcher/

inflating: dexpatcher/core_services.jar.dex

inflating: dexpatcher/dexpatcher.dex

inflating: dexpatcher/dexpatcher.jar

inflating: dexpatcher/hook_4.1-6.0_services.jar.dex

inflating: dexpatcher/hook_7.x_services.jar.dex

inflating: dexpatcher/zip32

inflating: dexpatcher/zip64

> patching services.jar

<< this might take a few minutes,

<< depending on your device's power

>> applying hook patch

info: read '/tmp/services.jar'

info: read '/tmp/dexpatcher/hook_7.x_services.jar.dex'

1 error(s), 0 warning(s)

!! dexpatcher failed

Updater process ended with ERROR: 1

I:Legacy property environment disabled.

Error installing zip file '/sdcard/TWRP/NanoMod-patcher-7.1.20170501.zip'
[Magisk] totalcmdext:
Android 5.0.1
[Magisk] Primokorn:
This is the longest zip I have ever flashed! I thought TWRP had freezed lol

Anyway I'm using a custom ROM having the signature spoofing patch so I don't need Nanomod (for now). But I wanted to test your module on another custom ROM which hasn't the patch.

It's working very well and it's very easy to use.

Kudos!
[Magisk] piet8stevens:
If you are trying to save it to /data, you must be root. Are you?

---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------

Deleted additional question in edit.
[Magisk] Anarchy16:
is there any possible way to sync contact from my google account ?
[Magisk] culiacanazo:
What? Here? Why wouldn't you? Download appropriate apks and happily sync away
[Magisk] Oswald Boelcke:
Certainly; despite me not using anything from Google. A search in the microG thread is going to guide you to possible solutions.

I'm grateful for the powerful search engine on XDA.
[Magisk] Anarchy16:
yup . already search . already tried flashable .zip and other blablabla files (the davdroid apk just save my ass)

anyway, thanks :) sorry for inconvenience
[Magisk] nihad15:
Does that signature spoofing patch work independently from magisk?
[Magisk] Oswald Boelcke:
XDA offers a fantastic search engine! ...or just go a few pages back in this thread; you're going to find the answer...
[Magisk] Setialpha:
I see, you haven't used the in-development version from the github repository, which already has several fixes. So I made a few more changes to the patcher. Find the latest version attached, please try again. Thanks.

Changes since the last update note:

* framework-patcher package: less verbose output from `dexpatcher` and `zip`
* framework-patcher package: note the user to post `/tmp/recovery.log` if something fails
* framework-patcher package: code clean-up
[Magisk] culiacanazo:
It should offer an "Auto Repeat" feature!

(i saw this "XDA search engine" thingie being posted not very many minutes ago! And the worst part is that that wasn't the last time it'll be posted!)
[Magisk] marcdw:
Yep. Also tried the patcher on ParanoidAndroid Lollipop 5.1.1 and got the error 1 thing. Haven't tried it on MM yet.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Magisk] totalcmdext:
Hi Again

I used the provided file but again the same problem.

I have attached the recovery.log.
[Magisk] Setialpha:
I'm currently test-running on my Tablet with MarshMallow and Lollipop ROMs. Let's see what causes the issues.
[Magisk] DodoGTA:
But, why doesn't it work? :p
[Magisk] m_reyna_16:
For some reason the Mozilla backend won't install, even if it's selected by itself and both... and I am unable to check these options (see screenshot). Contacts and calender won't sync (don't see the option) and I've selected them on the wizard and when checking safetynet I get an "unable to verify" error.

FYI, the error message may be off because I tried this last night and had to revert to my previous rom backup so I don't remember the specific words of the error message

I am running aex rom for oneplus 3 and it's a 8.1 rom if this helps
[Magisk] Setialpha:
There's no wizard for microG, I suppose it's either ROM or an artifact from GApps, if it's the latter, it can't work, because your ROM needs to be GApps free foruse with microG.

Also it says Unlp is not registered, what is the logcat? There's some other service binding location service already, either original GApps or some system service. What's inside /system/priv-app?
[Magisk] m_reyna_16:
Yes there is a wizard from nanodroid that sets up what to install... It's called the setup wizard zip and it's on the downloads section... I install that to set up what I want installed then I install the full version... Unless I'm saying it wrong but that's what I meant

It was a new rom so no gapps were installed and it's microg ready... I can't tell you what was on the log or on system/priv-app because as I stated, I reverted back to my old rom via backup... What I do know for sure is that I select, on the "setupwizard.zip", to install both backends and the Mozilla one doesn't install for some reason

If I'm doing it wrong then please let me know

EDIT: do you recommend to try and patch the system? Even though the rom is supposedly microg ready?
[Magisk] Setialpha:
Yes, I thought you mean the first run wizard in-rom.

No, AOSP EX is already patched, what I need to try to solve the issue is a logcat and information about the installed private system applications.
[Magisk] utg1:
Sorry for the dumb question .... But if I use 2 network location backends (Nlp) at the same time like Deja Vu and Mozilla UnifiedNlp, have I any benefits or is it redundant ?
[Magisk] kurtn:
Each backed reports an estimated error. NLP uses the position with the smallest error.
[Magisk] tom.android:
After I installed package "NanoMod-14.9.20171213.zip",it created "/data/apps/org.microg.gms.droidguard" . My problem is how to remove to /system/priv-app.?
[Magisk] Setialpha:
You don't, as it does not properly work as system app, thus DroidGuardHelper is installed as user app.
[Magisk] defi231:
cant use new nanopatchers

still cant use any new patcher after nanopatcher 14.9.2017

magisklog attached; TRWP " failed to apply patch "

i am on OP3T with lineageos from Sultanxda
[Magisk] Setialpha:
According to the log your ROM is already patched.
[Magisk] defi231:
yes it is patched with 14.9 want to apply the new patch 16
[Magisk] guest4711:
Either you install the new version without patching your ROM again -all should be fine then- or you restore the unpatched ROM and patch again. This should also work, there should be no differences to the other result, but it's a lot of more work...
[Magisk] utg1:
Anyone, with the new NanoDroid version, have issues with playstore? In particularly to enter in "my apps"??

Also in my (G)Maps doesn't work navigation....
[Magisk] American_Jesus:
No issues here with Play Store
[Magisk] Oswald Boelcke:
No issues at all with the Play Store.

Not using Google Maps but OSMAnd.
[Magisk] utg1:
Ok, solved play store issue..
[Magisk] godofsalt:
More info please. Like how you were able to have playstore working.

Thought that, it was to BBC work on this
[Magisk] :
LineageOS 15.1 not working, NanoDroid says Odexed

Hello [MENTION=4187311]Setialpha[/MENTION]

Long time NanoMod/Droid user, really like your work! :D

Unfortunately, since I updated my phone to LineageOS 15.1 NanoDroid wouldn't flash anymore :(.

I am using this ROM: https://xdaforums.com/oneplus-5t/development/rom-lineageos-15-1-oreo-oneplus-5t-t3730058

I have tried to flash the latest NanoDroid-patcher, the error I am getting is: !!odexed ROMs are not supported. This comes with an error 1. I understand what odexed is, but isn't LineageOS deodexed? :eek: I could not find odex files on my /system partition.

I have made TWRP logs but can't seem to be able to add them to this post. Do you need/want these logs?:confused:
[Magisk] Setialpha:
Yes, I'd need the log. In fact there are odexed LineageOS releases, search this thread, others reported that, too. Check if there are any idex files in /system/framework.
[Magisk] :
I have uploaded 2 log files to Dropbox:

- https://www.dropbox.com/s/uxxe4ssxeyi07wx/recovery.log?dl=0

- https://www.dropbox.com/s/0ddxm3nowkbp9cc/dmesg.log?dl=0

There are no files located in my /system/framework that have "index" or "idex" in their names. I hope these logs will help you with NanoDroid! :)
[Magisk] Shadow53:
Pretty sure "idex" was a typo of "odex" - so you may want to check again.
[Magisk] utg1:
I simply delete all play store data and cache and than restart.