yashsingh1/xdaforums huggingface dataset:
[Magisk] Ryū Kenden:
Sorry, I explained myself poorly. I'll try to be more accurate this time.

I installed a custom rom not long time ago, then I installed Nanodroid via TWRP, creating previously with the wizard the file with my preference (I.e. No debloating and no installation of extra apps). As far as I remember, I had no issue then. Then I upgraded with a dirty flash the rom and after that magisk flashed itself. It has passed some time, so I'm not quite sure if that's the reason or not. Because I never had to flash again nanodroid and I'm thinking that probably that's because of magisk that together flash also nanodroid.in fact, today I have noticed that in the menu module of magisk, were active both the nanodroid module and the systemless host. I never noticed that before so I tried disabling the nanodroid module. After the reboot the app missing were there but microG wasn't so I came to the conclusion that the problem was that. I'm not sure frankly.

What would you recommend? Unistall the module and flash again nanodroid via twrp?

And if I do so, what about next time I'll dirty flash an Update?

Thank you in advance

P.s if I may, why you wouldn't active the nanodroid module in magisk? For security reasons?
[Magisk] Apex Predator:
You need to manually flash NanoDroid in TWRP every time you install a ROM. Do not do anything NanoDroid related via Magisk manager (except to confirm its presence).

To be safe, before you flash, either run the setup wizard again or make sure its correctly edited files are on the root of your internal SD card, otherwise NanoDroid will install with default settings.
[Magisk] Oswald Boelcke:
Can't add anything to what @Apex Predator correctly stated.

In regard to your "P.S.": Certainly, my Nanodroid modules (I only use the µG-, BromiteWebview- and Fdroid-submodules) are activated in the Magisk Manager but this automatically occurs for me when I flash them via TWRP.
[Magisk] :
Got a banking app that suddenly siezed to work after ak update which implemented root protection. Which was easily fixed with hiding it. Though now it tells me I dont have network on, even though I do. I checked logcat an this was some of the things that came up:

10-01 16:03:27.837 E/no.dnb.vipps(7038): Failed to open APK '/system/priv-app/GmsCore/GmsCore.apk' I/O error
10-01 16:06:55.433 E/ResourcesManager(7038): failed to add asset path /system/priv-app/GmsCore/GmsCore.apk

Gmscore.apk obviously exists, as do its directory. I tried flashing microG again, but made no difference.

Any ideas on how to fix this?

Attatched logcat for further info.
[Magisk] githyanki:
Would really be nice if setup loaded previous setup, or offered to load it. If you don't want to change it your going to have to open the .nanodroid-setup (or others) file with an editor or you will lose your previous setup and have to put it all back the way you want.
[Magisk] Ryū Kenden:
I thank both of you. I'll keep this in mind in the future.
[Magisk] Anikscha:
Aurora store

Since the update (from Nano Droid Aurora Store to 3.12) of Aurora Store via F-Droid (Nano Droid Repository) the anonymous login failed, even so I have tried it several times !!

:confused:

Any idea [MENTION=4187311]Setialpha[/MENTION] ?

(AOKP ROM with SuperSU + NanoDroid-patcher-22.4.20190811 + NanoDroid-microG-22.4.20190811)
[Magisk] temporarium:
The guy behind the Aurora project has had server issues over the past few months. Try logging out and back in.

EDIT: I can confirm it's down again.
[Magisk] jumo0n:
Try this Token Dispenser in 'Network' options:

http://auroraoss.in:8080

Did the trick for me
[Magisk] :
I get handshake error with this token.

Are there more?
[Magisk] WiMiOP:
https://xdaforums.com/showpost.php?p=80414805&postcount=549

http://92.42.46.11:8080 worked for me where http://auroraoss.in:8080 didn't
[Magisk] Oswald Boelcke:
^^Confirmed! Sorry, out of thanks for this good advice.
[Magisk] rayman95:
Users of Note 3 have finally a functional Android 10 version, thanks to [MENTION=6561802]jprimero15[/MENTION].... But without nanodroid mod, no way.... Is there a way to flash last version without errors, or maybe we need root??!!

Anyway thanks for your work .
[Magisk] :
Nanodroid currently doesnt support android 10. And your rom has to support signature spoofing. Currently not every rom does this, so youd either have to patch this manually, or just wait. 'Cause nanodroid patcher wont work either.

Afaik there no Q rom that has signature spoofing already. SyberiaOS will have this in next built on op6, dunno about other phones.
[Magisk] amg314:
If ROM natively support signature spoofing, NanoDroid is not needed.

You can manually remove gapps using SD Maid and install main microG files.

https://microg.org/download.html
[Magisk] dhacke:
I don't have a android 10 phone yet but when i have it and the rom supports signature spoofing and i install microG with the files which you linked how must i do it to ensure microG has the right permissions?

As far as i know microG must be installed as system app. Can SD Maid make this for me?

Just curios.
[Magisk] Oswald Boelcke:
Certainly, any root explorer will do. I'm convinced the installation process as described here hasn't changed.
[Magisk] amg314:
SD Maid correctly remove apps and apps tails.

If you have gapps installed I recommend remove main gapps files using SD Maid.

After that install microG gmsCore. As I remember, it will install to /system/priv-app automaticly.

Then install gsf and fakeStore.
[Magisk] d1n0x:
Manually installed apps are NEVER installed in system/priv-app automatically, as /system is read-only by default. Just installing gmscore as a user app will also not make it work. You need to manually move it to /system/priv-app using a root file explorer or the TWRP file manager, plus give the right permissions.
[Magisk] amg314:
I think you're right, I apparently used Total Commander.

Permissions can be easily set similarly to other apps in /system/priv-app
[Magisk] PoochyX:
This is known facts

([emoji3590]09-09-18[emoji3590])
[Magisk] temporarium:
Moral of the story: just use NanoDroid. It'll do everything for you. There is a reason it came into existence.

Oh, and that's a known fact, too. ?
[Magisk] amg314:
NanoDroid is a convenient universal microG installer, especially for a beginner. However, in some cases it fails. In other cases, it is redundant (native signature spoofing or no gapps ROM).

In such cases, manual installation of microG helps - you can control every step of the process.
[Magisk] Oehrly:
NitrogenOS 10.0 for Oneplus 3/3T already supports signature spoofing.
[Magisk] d1n0x:
What?

Native signature spoofing support does not mean installing NanoDroid is redundant. In fact, it makes it even easier by not needing to patch it beforehand.
[Magisk] :
Great. I wasnt aware. SyberiaOS just released their new update aswell with signature spoofing.
[Magisk] Ismus10:
Anyone knows how to activate signature spoofing in omnirom 9?
[Magisk] d1n0x:
Yes
[Magisk] Ismus10:
and... how?
[Magisk] dhacke:
When i'm remembering correctly you can give the Permission in the microG setup.

It should be the first or second point from the top. Just tap on it and microG should ask for signature spoofing Permission.

Apart from that you can give microG the permission over the app permissions in the settings of the system.

Settings -> Apps & Notifications -> Tap on "Advanced" -> Permissions -> Spoof Package signature
[Magisk] thelad:
So does the 11/8/2019 nanodroid work on nitroOs 10
[Magisk] :
No, nanodroid doesnt support android 10 yet.

You have to install your packages manually
[Magisk] thelad:
Good stuffing thanks for clearing that up
[Magisk] Setialpha:
I'm going to test Android 10 on my backup phone, soon.
[Magisk] Setialpha:
Installing and Setup working fine. NanoDroid-Overlay is not properly executed during installation (Magisk 19.5-carnary, but fine on 19.4).

microG setup has a few hiccups, but stuff mostly works, like account login/Play Store/App Purchases and stuff.

NanoDrois fine on 10. Patcher not yet tested.
[Magisk] mircato:
whenever i try to patch the latest play store i get this message

patch: **** Only garbage was found in the patch input.

any idea how to get over this?
[Magisk] marcdw:
Why are you patching the Play Store? What is it that you are trying to do? Either way I'm quite sure it's outside the scope of this thread.

ZTE Axon 7 A2017U, AOKP 7.1.2 ROM, Radioactive v2.4 Kernel, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] Setialpha:
Some patches are just links to the actual patches, because the same patch can be used in more than one version.
[Magisk] mircato:
i'm following the nanodroid documentation ! what makes you think it's outside the scope of the thread?

https://gitlab.com/Nanolx/microg-phonesky-iap-support

and this's the link in case you wanted to check it

how should i proceed then? i'm using microg with fakestore now till i figure out how to solve this

also i tried to install the phonesky provided in the full nano package as system app using systemizer module but it doesn't work, only getting a loading animation

and i can't use aroma installer since my device doesn't support it, trying to boot into aroma gets me some kind of a bootloop

thanks for your reply
[Magisk] Setialpha:
What exactly are you doing? What release and what patch?

I've also uploaded a Script that does the patching for you in the aforementioned repo, feel free to give it a try.
[Magisk] Setialpha:
So Android Q introduced APEX files. I discovered, several Q ROMs use an APEX file for com.android.runtime. So, if that APEX file isn't mounted, issues may occur. In case of NanoDroid 'aapt' won't execute, rendering all installations unbootable because permission files get f* up. Guess what? CommonInstaller now checks for the com.android.runtime or com.android.runtime.release APEX and mounts it. While this is in early stages, I fixed NanoDroid Installation on crDroid 6 and LineageOS 17 on my OnPlus 5T. NitrogenOS 10 on my OnePlus 3T doesn't use APEX, thus works with 22.4 already.

A beta build with Q compat will be released this weekend.

Edit: will also come with nanodroid-overlay that supports /system/product debloating.

Edit 2: And installing Bromite WebView into /system/product, if required.
[Magisk] Setialpha:
Update on Q support: still a few hiccups to iron out regarding permissions of system apps. At least on LOS based ROMs, mistly effects accessing internal storage.
[Magisk] omerm007:
Thank you for your work!

Will the patcher be updated as well? If not, how can we get signature spoofing support on 10?
[Magisk] mircato:
I'm trying to patch phonesky 16.9.10 with the 16.9.10 diff file but it return the error mentioned above

I can send some screenshots when i'm near my computer if you want
[Magisk] azakosath:
A quick workaround for this is to manual reinstall latest μG core as an update, so it requests correctly the storage permission and it gets granted. I guess the same goes for all other system apps from Nanodroid installer.
[Magisk] Setialpha:
Yes, but that's ugly.
[Magisk] marcdw:
[MENTION=5149538]mircato[/MENTION], I was totally scatterbrained when I replied. Apologies for being a dope. [insert dunce emoji]

[emoji51]

Samsung Galaxy Light SGH-T399, CyanogenMod CM12 ROM, microG (NoGAPPS), XDA Legacy
[Magisk] d1n0x:
I am getting a "updating play support libraries" notification every once in a while which gets stuck on "installing" forever, but can be dismissed until it pops up randomly again
[Magisk] githyanki:
I would rather a way to ignore certain users. I guess down voting also would warn others about certain users.
[Magisk] TeLow:
You can ignore users but they still annoy you with a post saying this user posted something but he's on your ignore list, thus wasting data too.
[Magisk] derders:
here too

in NanoDroid's custom microG there was a fix for this ...

@ Setialpha how is it handled today after Official microG GmsCore is used and not your custom microG?
[Magisk] Setialpha:
The fix has never been in GmsCore, but Play Store itself. I haven't checked the code changes yet. You may block the update service.
[Magisk] lfom:
This stopped after I installed the latest vsrrson (from October) found in the F-Droid repo. It also has a black theme.
[Magisk] d1n0x:
I am on the latest version available via fdroid. It started after upgrading
[Magisk] kurtn:
What Nanodroid version did you install? My Lineageos 17 on surnia doesn not boot with NanoDroid-microG-22.4.20190811.zip. Neither after clean flash (OS and NanoDroid only in one TWRP session), nor after flashing a fine running system with today's magisk canary and smali patch.
[Magisk] Setialpha:
current git head.
[Magisk] kurtn:
So i wait for next beta?
[Magisk] Setialpha:
Either that or create a snapshot build on your own.
[Magisk] TeLow:
If i pull from git it says:

and it does not allow me to compile a package.

got any ideas how to fix it?
[Magisk] Setialpha:
Try downloading swipe stuff again.
[Magisk] TeLow:
Hi Seti,

ran the -pull and the u-swipe command, still says the same.

Cheers
[Magisk] raptorddd:
hi. i been away for a few weeks. i see transswarp is the latest stable. i have that but i keep getting play services libraries updates often. i have fdroif and theres no update. but still keeps downloadikg play services libraries.. why no stable updates.?
[Magisk] githyanki:
Where are you seeing these updates?

You did blacklist it in aurora, if that's what tour using, right?
[Magisk] raptorddd:
i dont use aurora. if you mean google services library well it just updates and i can see the notification on screen. i use google play.
[Magisk] pokipokipxorn:
If using MyAndroidTools Pro, can try to disable Play Store Services:

GMSCoreUpdateService

Not entirely sure it will fix it. While Play services was updating today, I disable the service and the update stopped immediately.
[Magisk] Helios747:
I have a probably weird question.

Is it possible to get your Magisk modules it installs separately? Your packaging of MicroG works better than anything I've been able to come up with, but TWRP for my device (Pixel 3a) has had no Android 10 support for quite awhile now due to partition changes breaking it and very little dev support on TWRP's side. So I can't install your packages anymore.

I can manually install Magisk modules though, as Magisk is still install-able through manual boot.img patching.
[Magisk] Setialpha:
You mean flashing through Magisk Manager? That caused issues, so was dropped long time ago. But Magisk evolved, many bugs fixed, so I might give ut a try again.
[Magisk] Setialpha:
Found a workaround for the Android 10 issue, that bundled apps, including uG, don't request storage permission and instead get it denied and thus don't work.

22.5 beta will arrive tomorrow, it's too late now.
[Magisk] hack_rid:
I want to run the setup wizard before I flash microg to make the play store available.

but each time it crashes shortly after I start the installation process from twrp (3.3.1-0)

setup wizard: NanoDroid-setupwizard-24.90.20191014.zip

the attached picture shows the screen shortly before the phone reboots without showing anything of the setupwizard.

sorry for the poor picture quality.#

can anyone give me a hint what I could try?
[Magisk] githyanki:
Some twrp versions do not support aroma installer, you may need to setup the files manually.
[Magisk] Helios747:
EDIT: what they said ^ AROMA based scripts have been broken in recent versions of TWRP for a pretty long time. You're better off manually configuring the installer through the config file you can drop next to the zip file on the device. I believe it's documented in the repo.
[Magisk] TeLow:
Hey Setialpha,

Thanks for the work man!

Question:

Latest google maps is bugging with the "please update google play services" message again, every time you open it. Where can I flag this issue, with you or with mar-v-in over at the microg repo?
[Magisk] rayman95:
you have to install V9.84.2 version, the last who works correctly..
[Magisk] azakosath:
[MENTION=4187311]Setialpha[/MENTION],

unable to flash on Xiaomi Mi A2, TWRP says "failed to mount /system (unsupported A/B device?)

# mount /system
# ls -l /system/system/bin/linker*
lrwxr-xr-x 1 root shell 36 2009-01-01 00:00 /system/system/bin/linker -> /apex/com.android.runtime/bin/linker
lrwxr-xr-x 1 root shell 38 2009-01-01 00:00 /system/system/bin/linker64 -> /apex/com.android.runtime/bin/linker64
lrwxr-xr-x 1 root shell 36 2009-01-01 00:00 /system/system/bin/linker_asan -> /apex/com.android.runtime/bin/linker
lrwxr-xr-x 1 root shell 38 2009-01-01 00:00 /system/system/bin/linker_asan64 -> /apex/com.android.runtime/bin/linker64
# ls -l /system/system/apex
total 133492
-rw-r--r-- 1 root root 314644 2009-01-01 00:00 com.android.apex.cts.shim.apex
-rw-r--r-- 1 root root 5339767 2009-01-01 00:00 com.android.conscrypt.apex
-rw-r--r-- 1 root root 5887723 2009-01-01 00:00 com.android.media.apex
-rw-r--r-- 1 root root 23337537 2009-01-01 00:00 com.android.media.swcodec.apex
-rw-r--r-- 1 root root 1778091 2009-01-01 00:00 com.android.resolv.apex
-rw-r--r-- 1 root root 99548678 2009-01-01 00:00 com.android.runtime.release.apex
-rw-r--r-- 1 root root 959961 2009-01-01 00:00 com.android.tzdata.apex

Edit: LOS 17
[Magisk] azakosath:
I used Smali Patcher.
[Magisk] Setialpha:
What's the output of 'ls -l /system/*.prop'?
[Magisk] daywalk3r666:
ls -l /system/*.prop

-rw-r--r-- 1 root root 4466 Oct 12 13:53 /system/build.prop

Gesendet von meinem One mit Tapatalk
[Magisk] azakosath:
# mount /system
# ls -l /system/*.prop
lrw------- 1 root root 23 2009-01-01 00:00 /system/default.prop -> system/etc/prop.default
# ls -l /system/system/*.prop
-rw------- 1 root root 2768 2009-01-01 00:00 /system/system/build.prop
[Magisk] Setialpha:
Hmmm... could please post the ibstallation logs?
[Magisk] azakosath:
Unfortunately logs don't show anything and when I flashed SystemTest, it didn't create any logs.

Edit: NanoDroid_24.90.99999999_twrp_.log is empty and didn't get uploaded.
[Magisk] daywalk3r666:
the patcher module didn't created any log.here is recovery log. hope this would help
[Magisk] Anikscha:
MicroG installation gone after ROM update !!

[MENTION=4187311]Setialpha[/MENTION]

I installed AOKP ROM with SuperSU + NanoDroid-patcher-22.4.20190811 + NanoDroid-microG-22.4.20190811 + a single Playstore from here...

https://androidfilehost.com/?w=search&s=PlayStore-patched

No problems ! Everything OK !!

No DF-DFERH-01 error !! License check of paid apps works !!

As I mentioned here...

https://xdaforums.com/showpost.php?p=80342091&postcount=7210

Today I installed the October update of AOKP by TWRP, but now, everything of the "NanoDroid-microG-22.4.20190811" installation is

missing

, as well the the Playstore App and the Playstore account on top!

So I installed NanoDroid-microG-22.4.20190811 and the single Playstore again.

(I used the that single Playstore out of the idea to install the minimum).

The self test of MicroG shows everthing is OK!

BUT, I can't create an Playstore account, even so I've tried several times!

No specific error appears, just "try later, a problem with the Google server".

Any idea?

Immediately I check Playstore with my other phone (same Playstore account) and it logged in successfully.

However, I flashed my full backup via FlashFire (Chainfire) and everything is OK, but of course, I'm back on AOKP September update.

Are there any known problems about/after a ROM update ???

G900F (AOKP ROM Nougat)

SuperSU 2.82-SR5

TWRP 3.3.1-0

Modem/Baseband G900FXXU1CQK3

Bootloader G900FXXU1CRA2
[Magisk] SH1M4BD3:
https://del.dog/anecoyulut

Gphoto crash any fix??or alternativesto sync my google photo??
[Magisk] kurtn:
I don't think it is a good idea to let Google host my private photos. I prefer keeping them on hard disks at home. If you really need automatic synching, there are FOSS solutions as well.
[Magisk] SH1M4BD3:
I found this Nanodroid lately, so that all photos 5years back already in google photos anyway
[Magisk] Some_help:
Andoid X86(_64)

I would like to enable microG on Android X86(_64) (Relese 2 of Oreo is now available) but I'm having problems enabling signature spoofing.

Here's what I've tried:

1) - Used Haystack and SmaliPatcher to try and patch services.jar but failed (since rom is odexed)

- Used vdexExtractor to extract services.dex and packed it back into services.jar. Still fails.

2) - Used Tingle to patch (deodexed) framework.jar (took dex files from boot-framework.vdex) but when I put it back and restart the signature spoofing is still not working.

I'm not sure what I'm doing wrong.

Maybe the first method doesn't work since services.dex were compiled for x86(_64) instead of arm?

Or the second method doesn't work because there are two dex files inside framework.vdex and I shouldn't pack both of them into framework.jar?

Or maybe, even if I managed to this the spoofing still wouldn't work because the entire room needs to be deodexed?

I'm very thankful for all the help.
[Magisk] SkyeNymph:
Can this be installed over a rom that already has microg safely using magisk mode?
[Magisk] user822:
For OMNI 10 on Oneplus 7 Pro I end up in a bootloop using NanoDroid-microG-22.4.20190811

Anything I can do to fix it?
[Magisk] Setialpha:
Yes, post your framework-res.apk.
[Magisk] user822:
Thanks for looking into it!

Not sure which hoster you prefer, all the same file:

https://files.catbox.moe/iyy5n6.apk

https://filehorst.de/d/cJaoxBHe

https://mega.nz/#!oEwCyQRC!6dKNBHswGvfTwSUHciem_vzSmLDXb7_bTwtq6GdL9XM

Edit:

I manually added a

privapp-microg-permissions.xml in /system/etc/permissions

including

And the phone is booting now

microG got permission to spoof the sigure after clicking the button in selfcheck, and "pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE" solved it for the fake store
[Magisk] Setialpha:
Yes, that's required, I need framework-res to do it automatically.
[Magisk] Valdrio:
Use syncthing or nextcloud and remove your photos from gdrive, no?
[Magisk] :
Thanks for this fixed my bootloop on lg v30 android 10 rom
[Magisk] githyanki:
Since the point of doing all of this was to not add a Google account, not sure what the problem is. Please be more specific about where your trying to add a Google account at specifically.
[Magisk] githyanki:
Did you install shadow53 play store last time, since that's how you would get the verification through play store.
[Magisk] Setialpha:
Not related to being unable to add a account. Edit: there's no shadow53 Play Store, those packages use mine (and that's stated over there).

What's the error message/log?
[Magisk] anvesh583:
[MENTION=4187311]Setialpha[/MENTION] My beryllium bootlooping after flashing 24.9 beta on Android 10. Systest module says invalid A/B partition while flashing zip . Plz help to fix the issue.
[Magisk] z99vwEfK:
I just installed nanodroid and made a mistake thinking yalp was dropped in latest stable, so I ended up with yalp store instead of aurora store. what's the easiest way to change this? do I have to do it manually or can I just make the changes to .nanodroid-setup and reflash nanodroid?
[Magisk] carlos974:
In Twrp mount the \system partition and after flashing Nanodroid.zip :good:
[Magisk] guest4711:
Yes, change the setup file and reflash.
[Magisk] refai:
Hi, would like to know which Android 10 you used? With the same phone, I have tested every available ROM but they didn't work. Please advice, I. Wanted to give a try.

About 18 ROMs working with Pie, tested and used it for fora week. link https://xdaforums.com/asus-zenfone-max-pro-m1/how-to/install-microg-asus-zenfone-max-pro-m1-t3953130
[Magisk] refai:
Wow, I didn't know that part, thanks for sharing, I will definitely try tomorrow and let you know.
[Magisk] NamitNayan:
You missed the BASIC.

Lineage OS microg version. (Comes with microg, and nanodroid will install fine over it, in case you need something more than microg, like patched play store etc)

I use it as it is, works good.

https://download.lineage.microg.org/X00TD/
[Magisk] methuselah:
[MENTION=4187311]Setialpha[/MENTION] magisk don't work on my phone. Its corrupts system. But i have got fully working TWRP. The stock pie rom is chinese ROM. My device is nubia red magic nx609j. Will this app work on my phone without magisk? I have OMNi but on that too. Magisk didn't worked.!