yashsingh1/xdaforums huggingface dataset:
[Magisk] bege10:
I had to move the app manually after flashing, it was still in the /system/priv-app folder. By the way: is it normal that the system folder is empty in the file manager of TWRP? I could only access it from LineageOS.

---------- Post added at 03:18 AM ---------- Previous post was at 02:49 AM ----------

When I flashed NanoDroid for the first time I had to run the separate patcher afterwards to make LineageOS support signature spoofing.

When flash newer versions of NanoDroid the system is already patched. But with every update of LineageOS the patcher runs automatically by a NanoDroid script. That is very comfortable. But the patcher version that runs remains the version that I ran manually the first time. So the current NanoDroid version differs from the patcher version used with system updates. Can this cause trouble? If so, can the NanoDroid script use the current patcher instead? If not, what do I have to do?
[Magisk] LovepreetSinghGill:
System file is empty in twrp because you the to Mount first the system folder. Go and see Mount in twrp and there you will see the system folder not mounted
[Magisk] demonoidmaster:
Lol you need to mount the system first
[Magisk] bege10:
Thank you, but, please, don't forget to answer to the second more important part of my question.
[Magisk] alecthenice:
Is your reply to me? That a screenshot of all my apps as shown in klizis post would help you evaluate if it will trip DM verity?
[Magisk] Oswald Boelcke:
I really apologise but I was busy with something else but pretty important on XDA, and eventually it became nighttime in the part of the world where I live. Then I really dared to go for a nap...:o

First before I focus on your issue, please allow me a few words in regard to DoR3M3's comment. The first two screenshots (SS) show how your and Klizi's posts look like on a PC browser. The next two SS are supposed to show how to add an attachment to a post but not to incorporate it into the actual "text part" of that post. And as it looks slightly different on XDA Labs, I also attached six SS in regard to the same subject.

Now to your issue. As your post only contains very little information I've to make some assumptions; however, as you know all plans collapse if the assumtions they were based on turn out to be wrong.

As the error notification states your already installed µG Services Core bears a different signature than the one of the Nanolx F-droid repo. The latter is signed by Setialpha while the original one is signed by MaR-V-iN. I assume that your installed µG Services Core is this original one, not knowing how you installed/flashed it. My personal initial solution would be to simply flash the NanoDroid microG submodule via TWRP what should replace any installed µG Services Core by Setialpha's one. After reboot to system update the Services Core through F-droid to the latest release.

No it wasn't! If you look at DoR3M3's post he clearly addressed oseiasrodrigues0.
[Magisk] elraffa:
If I use energized magisk module with Blu filter, Have I to whitelist mtalk.google.com?

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] ashwini215:
You can try this -

Uninstall fdroid, reinstall it, add the Nanodroid repository again & hopefully it should update fine .

worked for me when I had the same issue.

Additionally, you can also clear microg app's data and cache before reinstalling fdroid app.
[Magisk] elraffa:
hi, how can I fix microg core services wakelock?

Enviado desde mi ALE-L23 mediante Tapatalk
[Magisk] guest4711:
Why double posting? You'll get the same answer here as in the other thread: Disable GCM.
[Magisk] psychem:
device oneplus x

rom los16

using nanodroid microG - googlemaps isnt locking the location on maps. location locks fine on gpstest app.
[Magisk] DoR3M3:
No I Quoted oseiasrodrigues0

I was just kidding/playing around, I know you like to keep them in line... ;)

Cheers
[Magisk] Oswald Boelcke:
I'm convinced you have to. Like AdAway, Energized also uses the Hosts file.
[Magisk] LovepreetSinghGill:
Can I install nanodroid without even letting it detect magisk and not making it as magisk module
[Magisk] marcdw:
I believe so. Run the AROMA configuration tool first. There's an option to force system install. Should work.

ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] lucastracq:
i've been wondering the same. looking at energized blu hosts file in github there is no instance of mtalk.google.com

what do you think?
[Magisk] ColdUser:
I installed the Droid microG and playstore Working and everything.

Only API fault on Magisk with safetynet check, i check also with App Safetynet cheker and it does succeed but fail on response validiation.. Is this normal or do i to grant some permissions.

On Mi5 running Syberia ROM
[Magisk] iacchi:
I'm sorry to write yet another post on Bromite installation, but I can't quite figure this out (and probably it's me doing stupid things). This is my situation:

1. I'm using a Lineage Nougat rom (an unofficial one, I don't know if it's important)

2. When I updated NanoDroid a few weeks ago, I also flashed the Bromite zip via TWRP

3. On reboot, Bromite module is present in Magisk Manager, but I cannot select Bromite as WebView in developer options (only AOSP WebView is available)

4. Flash forward to now (couple of reboots in between)

5. Added Bromite repo on F-Droid and updated the app through it (I guess it means that the app is installed and recognised, it also shows up in the app list)

6. Still cannot select Bromite as WebView, though

7. If I look in /system/app/webview, the folder is empty except for a file named .replace, which is itself empty (I don't know if this is the work of NanoDroid)

8. I don't have a /sdcard/nanodroid_backups folder, which means that either the AOSP WebView apk was not backed up, or it was not replaced (?), or else

9. I have no clue where the AOSP WebView apk is supposed to be stored in the system (as it's not in the webview folder), but the Bromite one is in /system/app/BromiteWebView

10. A WebView test app indeed confirms that I'm still using AOSP WebView, based on Chrome 63

11. If I try to open the Bromite apk from /system/app/BromiteWebView, the installation fails because it says that the package might be damaged

12. If I download the apk again from Bromite website and try to install it, it installs without any issue, but I still cannot select Bromite as WebView, even after a reboot

13. If I try to install again from /system/app/BromiteWebView after installing from the Download folder, it still fails

Is it me doing something wrong or skipping some steps? How do I proceed from here?
[Magisk] guest4711:
Google changed the API in October (?). Perhaps your checker app is outdated... Update it or use another app for checking SN status.
[Magisk] marcdw:
[MENTION=4719100]iacchi[/MENTION], sorry you went through all of that but it was for naught. On Nougat there is nothing to change or switch to in dev options. Both Bromite and Chromium webviews will show up as AOSP WebView. There is nothing to select, nothing to do. You're good.

LG G3 D851, AospExtended v5.7 ROM, NanoDroid-microG (NoGapps), MultiROM, XDA Legacy
[Magisk] iacchi:
Do you mean that I have Bromite installed and active, or that I cannot install it? In the second case, well, too bad. In the first case, though, I think you're wrong. I installed the WebView Test app and it says that my active WebView runs on version Chrome/63.0.3239.111, While Bromite version installed is 71.0.3578.85, which I guess matches the number of the Chrome(ium) version. So, I don't think I have Bromite active as WebView system.
[Magisk] marcdw:
Hmm, interesting. If you do not have a /system/app/webview/webview.apk on your system yet the testing app says you have v63 I can only assume you have either Google's webview somewhere or you're also running Google Chrome (which takes precedence as the webview provider on recent Androids though I doubt you'd run a copy that old).

You can check in Settings' app list to see if there's another webview other than Bromite installed.

EDIT: Strike all the above. What a dope I am. I forgot that Bromite obfuscates / masks information. For instance the webview testing app or a site like html5test.com will not return true values. It is privacy oriented after all. For instance if you go to the above site, in a webview based browser, you'll also see your device is masked as something else. Mostly Samsung in my case.

On this ROM they show chrome/67. Eelo ROM (LOS Nougat) on my Axon 7 shows chrome/63. BalanceOS on another device shows v67.

I literally run over a dozen ROMs across three devices (multiboot addict) where most run Bromite or Chromium webview. Manually replacing system webview while in TWRP after flashing a ROM. 100% sure of no conflicts.

Later on I'll boot into the different ROMs to confirm what I believe is the case.

LG G3 D851, AospExtended v5.7 ROM, NanoDroid-microG (NoGapps), MultiROM, XDA Legacy
[Magisk] LovepreetSinghGill:
Flash the magisk module saftey. Net v2
[Magisk] iacchi:
Ok, that makes more sense now, thank you for the information. Now I think I believe I have Bromite running. The useragent reports itself as a Samsung J7 Pro with a Safari web browser (which striked me as odd before), so I guess this is Bromite's obfuscation feature. Thanks!
[Magisk] marcdw:
Yeah. I rechecked the Bromite browser feature list and forgot it has always-incognito mode. The webview has most of the browser's features.

ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] lucastracq:
do you plan at some point to include bromite webview in the full package? if not, why? i'm curious because it's the only thing that you don't include, if i'm not mistaken. thanks in advance.
[Magisk] bertino:
Is there any advantage to installing osmand as system?
[Magisk] Setialpha:
9.3 beta2

Version 9.3 beta2 is now available. Changes since 9.3 beta1:

* Internal Changes
* re-signed microG GmsCore and Phonesky with my own key instead of debug key
* work-in-progress: x86/x86_64 support
* Updates
* Lightning (4.5.0~snapshot)
* self-built; signed with my own key

Yes, the Full package size has now noticeably (up from 180 MB to 247 MB), that's the prize for x86/x86_64 support. In fact it's that VLC has a separate build for every architecture, so it's bundled 4 times (the installer detects your device's architecture and installs the proper one), and that's what (mostly) increases the package size. I'm currently considering dropping VLC from the Full package, but I'm undecided.

Anyone interested in x86/x86_64 support should test the Full and Patcher packages (if applicable), I don't own a x86/x86_64 device. The full package should be fine as it is now, but the Patcher may not work (yet).

Download from AFH.

[MENTION=5314340]Wo11ven[/MENTION]
[Magisk] knpk13:
I noticed that nanomod has an uninstaller zip. Will all changes be reversed if we simply disable nanomod in magisk manager? Or do we also have to flash the uninstaller zip?
[Magisk] Setialpha:
Uninstalling from Magisk is enough.
[Magisk] Wo11ven:
Thank you very much for this!

Just tested the patcher, and it did fail. However, I did also test your old 6.2-test2 patcher and it seems to have worked, but I'm still waiting for the device to boot.

Attaching my recovery.log with both flashes.

My device is a Zenfone 2 Z00A x86, running RR 7.1.2.

Edit:

So, the device wasn't booting because of the full package. I uninstalled it and it booted in no time. Then I tested the microG pack and it also bootlooped. The f-droid pack works!
[Magisk] Setialpha:
Edit: --deleted-- see next post.
[Magisk] Setialpha:
NanoMod 9.3 beta3 now available, featuring several fixes regarding x86/x86_64 support.

Download from AFH.

Please test at least Full and Patcher packages on x86/x86_64.

In case it does not work or there issues on x86/86_64 please provide recovery.log and logcat.
[Magisk] Wo11ven:
Full pack still leads to bootloop, attaching logcat from ADB.

The patcher also still fails, the recovery.log is the same as the one in my last post.
[Magisk] Setialpha:
What's the recovery.log for the full package?

Device is x86 or x86_64?

What ROM and ROM version (not Android version)?

What version of Magisk?

In fact your bootloop looks like one I had with one of the early v13 beta builds, but it eventually got fixed.

That's the reason NanoMod initially didn't have x86/x86_64 support, it's difficult to fix something when you're not in charge of a device. It may take some time until all issues are ironed out.
[Magisk] Wo11ven:
-It has support for x86_64, but everything is built in x86, if I'm not mistaken. Maybe seeing this will help?

-ROM is Ressurection Remix N 5.8.3 official, build from 06/08.

- Magisk is v12, the one that comes with RR.

A new build for my ROM just got released, will update and provide the recovery.log for the full pack.

Edit:

Attached recovery.log for full pack. Btw, I also edited the information I provided about the device architecture. [MENTION=4187311]Setialpha[/MENTION]
[Magisk] Wo11ven:
Ok, so now I'm running LineageOS and I've tested your full package without magisk and it works. Still stuck in boot animation when using Magisk.
[Magisk] Setialpha:
What version of Magisk?
[Magisk] Chocklety Boyee:
Guys ..flashed latest beta on my redmi note 3 resurrection remix nougat 7.1 and enabled properly everything ..disable battery optimization ..enabled safetynet..play store works fine but when I try to check for safety net it says attached error ..can someone help me plz..I just want to pass safety net being on micro g ..
[Magisk] marcdw:
Google has updated their SafetyNet. At the moment folks all over are experiencing the same thing. You'll have to wait. The Magisk folks are working on it.

ZTE Axon 7 A2017U, AospExtended v4.3 ROM, Llama Sweet Kernel, NanoMod-microG (NoGapps), Tapatalk 4.9.5
[Magisk] Setialpha:
You did not setup microG, read the docs.
[Magisk] marcdw:
Oh yeah, and that too. LOL.

Other notes: I mentioned in the past that flashing NanoMod-microG sans Magisk (system mode) kept giving me Yalp Store instead of Play Store. I would test again with following betas up to 9.2 release with same result. Missed the last two betas and just got around to the latest. Play Store is now installed on the couple of ROMs I tried it on. Nice.

Now I get to setup another microG ROM using its built-in root.

?

ZTE Axon 7 A2017U, AospExtended v4.3 ROM, Llama Sweet Kernel, NanoMod-microG (NoGapps), Tapatalk 4.9.5
[Magisk] Wo11ven:
12
[Magisk] Setialpha:
Just a quick heads up: with the lastest Magisk v13 beta you can pass SafetyNet with NanoMod, when installed in system mode instead as Magisk Module. There's currently a bug with the hide_daemon, logs have been posted to topjohnwu from various users as of now.

To install NanoMod in system mode, do

uninstall NanoMod Magisk Module(s)

in TWRP rename /data/magisk.img to something different

install NanoMod (since /data/magisk.img is not found it will be installed in system mode)

rename magisk.img back to /data/magisk.img

re-run NanoMod patcher (if ROM is not pre-patched for microG)

reboot and pass SafetyNet

[MENTION=5314340]Wo11ven[/MENTION] did you give Magisk v13 beta a try yet?
[Magisk] digitman xxx:
is that equal to flash NanoMod before flash magisk?

ask that because i flash new rom now.
[Magisk] Setialpha:
Of course.
[Magisk] digitman xxx:
ok will give it a try then report status of SafetyNet

just inquiry about future update of NanoMod's installation will be like this way you refer in above post every time i install new update for NanoMod in order to pass SafetyNet.?
[Magisk] Setialpha:
Too big, that's why.

No.
[Magisk] kryosan:
Has the latest microG already fixed mega-thick lines in map apps?
[Magisk] d1n0x:
What??
[Magisk] kryosan:
:rolleyes:

https://github.com/microg/android_packages_apps_GmsCore/issues/236
[Magisk] marcdw:
Hah. I have never seen that on any of my Osmand and Magic Earth installations. Guess they don't use the maps api(?).

That is weird, and trippy looking.

ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy
[Magisk] alecthenice:
Im worried about installing the magisk module to a tablet with a cherry trail atom x86 chipset android 5.1 the epson moverio bt-300. I desire google gsf for using maps to support another app (mini map in drone aplication) i worry because i cant figure out a way to restore it other than warranty. Im not dumb by the way hahaha it doesn't have a button option to reboot to recovery and wheb i can get it to reboot to bootloader mode it wont boot to recovery... "Fastboot boot.... Whatever" not the point though what do you guys think about this module compatability? How do I begin to research compatability? Thank you for your time
[Magisk] jenslody:
Both use their own maps based on openstreetmaps data, not google-stuff.
[Magisk] Setialpha:
Basically it should work, but without recovery it's a bit difficult. Fastboot is only for bootloader, does 'adb reboot recovery' work (device needs to be booted for that)?
[Magisk] bege10:
New NanoDroid version with old patcher version?

Hi, maybe this question from 12/6 got lost, I hope someone knows an answer. Thank you:

When I flashed NanoDroid for the first time (no Magisk) I had to run the separate patcher afterwards to make LineageOS support signature spoofing.

When flash newer versions of NanoDroid the system is already patched. But with every update of LineageOS the patcher runs automatically by a NanoDroid script. That is very comfortable. But the patcher version that runs remains the version that I ran manually the first time. So the current NanoDroid version differs from the patcher version used with system updates. Can this cause trouble? If so, can the NanoDroid script use the current patcher instead? If not, what do I have to do?
[Magisk] alecthenice:
The crazy thing is that that command doesnt work with stock recovery. Perhaps if I flashed a twrp that a user has reported to work then the command reboot recovery would work?

I was trying to understand if this was a command to like instructions within the bootloader or to the recovery. Thank you for your thoughts
[Magisk] :
people who using magisk v18 can you pass safetynet? for me fail for both.
[Magisk] Setialpha:
The addon.d gets installed as part of the Patcher zip. If it works, there's no need to change it, if you still want to, though:

a) remove /system/addon.d/70-nanodroidpatcher.sh and /data/adb/NanoDroid_Patched

b) Flash ROM

c) flash new Patcher zip to patch services.jar and update addon.d

Yes, you need TWRP, stock recovery won't let you flash most zips, unless they are signed and also it's lacking many things TWRP includes. So if there's a working - and safely flashable - TWRP for your device I highly recommend using it (regardless of NanoDroid).

That's what I also discovered (and mentioned in the 20.3 announcement post) Magisk 18.0 changes several things in a very good way, but also introduced a few new bugs. Downgrade to 17.3 (only Magisk itself, you can keep Magisk Manager 6.1.0) and it'll be fine again.
[Magisk] :
Oh i missed that post, good to know, thanks!
[Magisk] jenslody:
Yes, but not using full nanodroid, just microg from the f-droid repo with systemized droidguardhelper (terminal systemizer) and MagiskhidePropsConfig-module. Signature spoofing is build in the rom (Bootleggers Pie on J5 FN).
[Magisk] alecthenice:
Yes, you need TWRP, stock recovery won't let you flash most zips, unless they are signed and also it's lacking many things TWRP includes. So if there's a working - and safely flashable - TWRP for your device I highly recommend using it (regardless of NanoDroid.[/QUOTE]

1) does that apply also to modules flashed through magisk?

2)

Does the command "fastboot reboot-recovery" normally boot to recovery? On my nexus 6p this occurs but it has twrp. Anyone have any insight here?
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] I'm using Super'Rs KItchen, the donate version, and when I deodex the rom, and then use the mods_install plugin and add in the NanoDroid-patcher to patch the rom, I see NanoDroid-patcher flash ok in TWRP, but when I try to boot the rom it won't start.

SuperR. has pointed out to me for problems like this to contact the developers and ask them to support this type of flashing.

Could you please look into this and if there's an issue with NanoDroid-patcher not supporting to work with Kitchen, can you please make it work?

Here's a recent reply I made regarding this;

https://xdaforums.com/showpost.php?p=78384155&postcount=2466

I really appreciate you looking into this.

Thanks
[Magisk] iacchi:
I've tried to search in the thread, but I don't think that this has been reported before. I updated from v.20 (20.1?) to 20.3 and now there's the new Simple Gallery Pro. The problem is that the old Simple Gallery (v.5.1.3) was not removed and now I have both versions installed. I'm not quite sure of the installation path of the old Simple Gallery, so I don't know how to delete it. It's installed as a system app, so I can't just uninstall it from the app manager.
[Magisk] h_maharaj:
I was having the same problem but managed to solve the issue on my end by making a boot script in service.d and adding the following packages to the hide list:

#!/system/bin/sh

magiskhide --add com.google.android.gms.unstable
magiskhide --add org.microg.gms.droidguard

After doing this both basic integrity and cts passes.
[Magisk] clewis.it:
Thanks for that. Instead of that, I checked the droidguard and microg services proxy in magisk hide and safety net passes now.
[Magisk] Setialpha:
It's the same path, because the system app has been replaced with the new one. You can simply remove the old one, as it's normally a user app (update).

Oh, I see, haven't yet tested anything, so it's safe to update, yay! Edit: DroidGuard Helper alone is enough, GmsCore is always on the hide list. Will add this to the issues list.
[Magisk] Setialpha:
I'vd uploaded version 20.3a of the Setup Wizard. Fixes selcetion for uNlp Backends not properly created.
[Magisk] d0s1s:
In my case, I fixed this situation with two steps:

1 - Using Magisk Hide for DroidGuard (this causes DroidGuard crash).

2 - To fix the crash... running like root --> pm install -r /system/app/DroidGuard/DroidGuard.apk`

SaffetyNet passes on latest nanodroid-microg build on OmniRom for OnePlus 6 and Magisk v18.0.

Regards
[Magisk] NamitNayan:
You can simply install apk like any other app in case 2.

It fixed for me.
[Magisk] Apex Predator:
I was just coming into the thread to post about the Mozilla back end not being installed despite being selected in the installer. Glad to see you've fixed it.
[Magisk] alecthenice:
Will this work on a device that has both android 5.1 sdk and an aditional moverio sdk? I want to install the magisk module so that i can use the backend of the google play enviroment. Is deoxing the rom all that is needed for compatability of devices among all devices within the specified supported sdks? I ask because my thread of like 6 on this device only includes amateurs. I have magisk and a twrp that is modified to suit my device I havent flashed it yet though because it requires a mouse to use. It should probably be flashed?
[Magisk] iacchi:
Hi Setialpha, that's the point: I can't. Both the old Simple Gallery and Yalp (I've switched to Aurora) are still considered system apps and the uninstall option is not there. The same thing didn't happen with Simple Calendar (I just decided that I didn't need it anymore, so I removed it from .nanodroid-apps), where after the update it was switched to a user app and so I was able to remove it.
[Magisk] forjustin:
Use root Toolcase app from xda.
[Magisk] derders:
[MENTION=4187311]Setialpha[/MENTION]

google play support libraries updates often a day at the moment... isn`t the fix to update microg version number to a higher one?

I am on latest updates of your microg that comes via fdroid (repo)

0.2.6.14797-dirty-113
[Magisk] Oswald Boelcke:
@Setialpha: Unable to confirm @derders observation. Also on µG Services Core v0.2.6.14797-dirty-113 (via F-Droid) and zero attempts of updates of the Google Play Support libs. Maybe it differs from device to device and/or overall system setup and configuration?