yashsingh1/xdaforums huggingface dataset:
[Magisk] rubino25:
There's a way to create the config file without aroma installer? On one plus 6 it crashe twrp, but I need contact sync! I'm on hydrogen os! Thanks..
[Magisk] tom.android:
nanodroid_microg=1

nanodroid_fdroid=1

nanodroid_apps=0

nanodroid_overlay=0

nanodroid_zelda=0

nanodroid_mapsv1=1

nanodroid_init=0

nanodroid_gsync=1

nanodroid_swipe=0

nanodroid_forcesystem=0

nanodroid_bash=0

nanodroid_nano=0

nanodroid_utils=0

nanodroid_fonts=0

nanodroid_play=1

nanodroid_nlpbackend=3

one per line and save file name .nanodroid-setup (dot nanodroid-setup) ,place it in root of internal storage .

(Magisk mode)
[Magisk] d1n0x:
No, you don't need contacts sync. Save your contacts locally in a vcf file and restore them when necessary. Why use MicroG and still give other people's data to Google?
[Magisk] Setialpha:
Is FakeStore actually installed? Go to Settings > Apps > All Apps > Show System Apps and check for Fake Store, if not, check the value of 'nanodroid_play' in your configuration and note that in 17.9 by default Yalp Store is installed without Fake Store. From the ChangeLog:

* value `2` for `nanodroid_play` will now only install Yalp Store
* new value `4` for `nanodroid_play`, will install Yalp Store and Fake Store

So if you've had it at 2 previously you'd want to use 4 instead, to install both, or 3 to only install FakeStore.
[Magisk] Setialpha:
I've uploaded new builds for microG GmsCore (0.2.4-128) and modified Play Store (11.4.15), to update issue, on-device, as root:

nupd ps
nupd mg
[Magisk] HyperCriSiS:
Is there any hope that WhatsApp and Threema GCM registration will get fixed?
[Magisk] d1n0x:
This has nothing to do with MicroG and can't be "fixed". These apps have migrated to Firebase, which is not (yet?) supported by MicroG.

Disable battery optimization for these apps and they should work.
[Magisk] DoR3M3:
I'm not sure what you mean about neither? FakeGapps allows Play Store (Phonesky) has correct signature to be enabled.

I said I have FakeStore installed, it doesn't help with Play Store (Phonesky) has correct signature...

I installed FakeStore, it doesn't help, and I thought this is a GmsCore issue.

Ok...

Thanks
[Magisk] NamitNayan:
already told you how to give proper signature spoofing permission to fakestore, but you find xposed way easy ,I can't help you with that.
[Magisk] DoR3M3:
I told you before I did this already and it does not enable Play Store (Phonesky) has correct signature.

Settings > Apps > Permission > Signature Spoofing > microG Services Core

If you noticed Setialpha said he made an update to microG, maybe that will help, or using YalpStore instead of FakeStore...
[Magisk] NamitNayan:
I told you to tap 3 dot menu,show system apps,then give spoofing permission to fakestore/phonesky.(the place where you see microg services core,do it there)

but since you ignored it,enjoy xposed.
[Magisk] HemanthJabalpuri:
Sir my issue from https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/post77390716 fixed?
[Magisk] tom.android:
After applied. Working cause I used china ROM (Beta MIUI-10 CN Dev v.8.8.23 ) in which always can't pass device certification..
[Magisk] DoR3M3:
I didn't ignore anything, I misunderstood.. I have it now, my bad before... :(

Should microG Services Core also be enabled?

Hmm need Busybox for nupd mg... I'm assuming the systemless way of Magisk for BusyBox is the way to go...

[MENTION=4187311]Setialpha[/MENTION] on Essential with NanoDroid-microG-17.9.20180818, I tired updating nupd mg with BusyBox 1.29.2 installed from Magisk and it failed.

/sdcard/nanodroid_apk/GmsCore.apk exists...

Please see the screen shots.

Thanks
[Magisk] Setialpha:
The download stopped at 6% for whatever reason, just try again.
[Magisk] mongo0:
hello,

since v...0818 playstore is always updating itself (gmscore, or something...) when rebooting and after running sometime. It is draining battery as well as data...

I disabled dailyhygieneservice a long time ago and it is still off, so it must be something else..?!
[Magisk] HyperCriSiS:
Any hope that GCM for WhatsApp and Threema gets fixed?
[Magisk] guest4711:
See https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/post77420257
[Magisk] d1n0x:
I already replied to you before in this thread.
[Magisk] Setialpha:
Update it, as posted a few posts back (and every time an update drops), in a shell on-device, as root, using 'nupd ps'.
[Magisk] Setialpha:
While baksmali crashes on Android 9, the Patcher works, after manually deodexing services.jar and putting it to /system/framework. Will check Android 8.1 next.

I will write together a doc on how to manually deodex services.jar, soon™.
[Magisk] tom.android:
Waitting.
[Magisk] NamitNayan:
You give permission to microg services core to compensate for play services, and to fakestore to compensate for play store.
[Magisk] Setialpha:
So, the status for on-device or on-pc auto-deodexing can be be followed, here: Signature Spoofing on Odexed ROMs - Status, Explanation. It's not a full-fledged documentation (yet), but better than nothing.

Also the current git version of the patcher will no longer abort on odexed ROMs and no longer marks SDK 28 (Android 9.0) as unsupported. Feel free to test, if you're brave enough.
[Magisk] HyperCriSiS:
Sorry, XDA App did not show my post, so I thought it got lost.
[Magisk] starbright_:
My framework.jar is only 310bytes, so my ROM is odexed, right?

I have a /system/framework/framework-res.apk ...

It seems the framwork patcher doesn't work here. Same for tingle. How do I get my ROM ready for spoofing/microG? Please help!

Edit: Just read the post on top of the page. I am on 8.1, so it is probably bit different. Not as easy for beginners....

Can you give some recommendations/comments?
[Magisk] DoR3M3:
Ok

Ok Thanks...
[Magisk] Setialpha:
Getting closer on Pie, ROM has location issues with GApps, too, so I can't say for sure yet, if it's a ROM issue or unlp issue, that I don't get a location (yet).

Also GApps removal mechanism changes in the upcoming 18.0 made it posdible for me to dirty switch from an GApps ROM (Pixel Experience) to microG, without needing to wipe data or anything. I suppose NanoDroid's GApps handling is now pretty close to it's goal.

Also nanolx.org gas some hiccups, wait until (much) later today, it's past 1 AM here, so I won't check for the next few hours.
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] have there been server issues, or congestion at times limiting this update?

I spent around 2-3 hours trying it over several times, till it finally downloaded...

I see it's pulling from wget, unless maybe an issue with it, or the BusyBox Magisk Module...

Downloads through Magisk, F-Droid and surfing the web all work fine on the phone...

Hmm
[Magisk] tom.android:
Good news
[Magisk] sxml2015:
No patches, why are some apps available for registration?

Wechat can't register?

Microg, I only need

Google Cloud Messaging GCM feature.

Odex ROM is very troublesome.

How to operate can not require patches, use gcm.
[Magisk] inVain_theGenuine:
if you can find "oat" folder within the framework folder, then you have an odexed rom.

the NanoDroid patcher do not work with an odexed rom.

if your current rom is supporting signature spoof natively, then you don't need NanoDroid patcher.

there's an app which can be found on fdroid, it's called "signature spoof checker" (please CMIIW, I can hardly remember the name).

the app can also be found on the xda forum (which again I can't remember where :D)

repeating the mostly repeated answer,

the easiest route to get sig spoofing for uG is by using exposed.

you'll lose SkyNet certification by having exposed installed, but since uG itself has been struggling with the SN lately, I'd say; "all out offense".

I used to passed SN with uG & omnirom, though.
[Magisk] starbright_:
Yepp, found an oat folder. I have asked the maintainer of A3 (2017) why it is an odexed Rom (on other previous devices I had it was not) and asked to include the spoofing patch. But this is rather longterm.

MicroG itselfs give a spoof (or better not spoofed) message.

Thanks for the hint (and patience) with the exposed framework. Well it is a mighty tool, but somehow I don't feel too well with all this things I don't understand. But seems I have to.

Reading that

https://gitlab.com/Nanolx/NanoDroid/issues/9#note_96779340

might be an option (https://xdaforums.com/showpost.php?p=77429490&postcount=3659)

Right now I am not sure I get this working, as it describes P (and I have O).
[Magisk] guest4711:
Signature Spoofing Checker (Test the signature spoofing capability of your OS) - https://f-droid.org/app/lanchon.sigspoof.checker
[Magisk] inVain_theGenuine:
you nailed it! :good:

ahhh....

I always sucks whenever faced with java, phyton, and such since I worked with ms. windows.

tingles, haystack, and everything else went "fubar" when I tried them out, I can't event edit a system.img of the android 7 with the available tools on the internet :LOL

I still got lightyears to catch, for setting up the environments only @.@

I'm afraid I won't be much of a help in this regard, sorry.

last time I heard the uG was able to pass the SN again, I really eager to give it another shot.

I was planning to use the official LOS 15.1 and taking the services.jar from their uG version, and use the NanoDroid to take care on the uG part (LOS update might break everything, though).

but since google had the upper hand again, I don't know...

lately, the pico version of Open GAPPS is behaving quite nicely and really easy to setup compared to uG.

coupled with NanoDroid to modify my system apps, I think I already had what need.
[Magisk] starbright_:
I tried now a few times Xposed and Magisc to get microG working. Once it seems everything to be ok (passed all checks in microG) but then I come into endless bootloop. Firewall don't get root permissions .... It was a mess. I think this two mighty complex tools doesn't work well with each other.

Trying it again the old way, LOS, addsu. Let's look how to proceed with spoofing and than manually add microG.
[Magisk] Koont:
Anybody tried to use Saiy open source voice assistant? It's requiring that I install Google for voice recognition, which defeats the whole purpose of Nanodroid. So, any alternative suggestions for a voice recognition
[Magisk] Setialpha:
So, I've now posted the instructions for VDEX. If you can see /system/framework/oat/[arch]/services.vdex, then this is for you.

VDEX deodexing instructions

Edit:

now part of the documentation.
[Magisk] ydd0ras:
Hello Herr Nachbar, had just successfully deodexed the services.jar on my Redmi Note 4x with the unofficial LOS 16 (Android 9).

Was also able to patch it and have now a spoofed signature. Yeah, finally! No need to study and try tons of deodexing tutorials and progs (noob!) And could have it on LOS or AOSP!

Will try the same on my Mi A1 with A/B system.

Many thanks!
[Magisk] Setialpha:
One step closer, vdexExtractor, baksmali and smali now working on a real device, though I don't know whether it'll create a proper services.jar.

Will try a few different things. Drawbavk, it's awfully slow. PC preferred for flashaholics.

Fingers crossed.

Edit: no, this is not beta1, it's a newer build, not yet released.
[Magisk] ydd0ras:
Looks very promising, the new build. I hope it works!
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] I've been reading around through the DOCS;

https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md

nanodroid_overlay=[0|1]

https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/GAppsRemoval.md

So I used nanodroid_overlay=[0|1] and I see Gapps gones, so I'm assuming rooted with Magisk, this is the pseudo-debloat feature?

Thanks
[Magisk] tom.android:
Please add howto recompile ,compile vdex.
[Magisk] HyperCriSiS:
Can't microG package debloat?
[Magisk] DoR3M3:
What if you have both services.vdex and services.odex ? :eek:

Stock Oreo on Essential has both...
[Magisk] starbright_:
[MENTION=8546761]inVain_theGenuine[/MENTION]: I followd your suggestion. I installed the Xposed Module FakeGApps, that should help spoofing an odexed ROM. After that I installed nanodroid-MicroG.zip

Now the strange thing. While the fdroid spoofchecker reports red: spoofing disabled the microG selfcheck give me an ok in the selfcheck!?!

Altogether it behaves strange. Sometimes I can log in anonymously via YALP/Aurora, sometimes not. But even if I can, it reads the list of apps, but I can't download.

As I can't download from the playstore I recovered apps via TitaniumBackup, but they have FCs. :(
[Magisk] pavanmaverick:
I'd love to give this a go on Pie - but building from Git is a little beyond me at the moment. Does anyone have the vdexExtractor built from Git that they could upload here? Thanks!
[Magisk] Ice Fire:
Hello.

I just read the information/instructions on how to stop the high batterie drain microg has when installed on an already used android device.

I have a few questions concerning that:

-does this still apply

-does this apply to updating microg.

-can i also fix this problem by deleting the cache via twrp

Best regards

Edgar
[Magisk] inVain_theGenuine:
exposed don't grant sigspoof to the rom, it just add a module so the uG don't complain about the lacking permission.

you should check the uG settings and see wheter or not you have all the check marks.

your yalp seems rather strange.

so I have a device with the chinese miui (without any playstore /google stuff), I'm still able to download the apps and install it to my phone with yalp.

all I did was assigning the proper permissions for the yalp store (storage & install from unknown source).

I don't plan to populate my device with yalp, by the way.

but yalp store is quite handy to check whether or not an app is gms dependent.

I'd rather have my apps downloaded from apk mirror.

I never used the titanium backup, whether if I'm with the uG or gapps.

and from previous reading, lots of people runs into issue when they are restoring their apps with the TB.

you should setup the uG properly first.

after you get it done, you can start to populate the apps.

failure to do this will only lead to frustation, just trust me on this one :D

the patched playstore bundled with the NanoDroid is the easiest way to register a device and populate the app.
[Magisk] Souvikhazra80:
[MENTION=8546761]inVain_theGenuine[/MENTION] I am using NOS P on Zuk Z2 Plus.ROM is deodexed(Confirmed by dev),but still 18.0 patch not working :(.
[Magisk] Souvikhazra80:
Using NOS P,ROM is deodexed(Confirmed by dev) but still 18.0 patch is not working:(.
[Magisk] Setialpha:
logs?
[Magisk] HemanthJabalpuri:
[MENTION=4187311]Setialpha[/MENTION]

Sir my twrp error 1 i.e., busybox issue fixed..in latest beta but in microg signin setup wizard signin and cancel options are not recognising the tap....

so i am not able to press signin option....

I am on Stock touchwiz 4.4.2

sir I think uninstaller also need busybox..

since uninstaller also gives error 1 in twrp....
[Magisk] Setialpha:
Patcher 18.0~beta1+vdex

EDIT: Find a newer test-build [url"https://xdaforums.com/showpost.php?p=77443818&postcount=3697"]here[/url]!

it's_hapening.gif

The Patcher should now be able to

deodex services.jar

patch services.jar

create addon.d

I've succesfully real-life tested it on LineageOS 15.1 on Nexus 6, which is a vdexed ROM. I don't have a older odexed (non-vdexed like Nougat) ROM tested yet, though the code is in place.

Credits go to anestisb for vdexExtractor, JesusFeke for smali/baksmali and Lanchon for dexpatcher. Feel free to test and report back.

Friendly reminder:

bug reports without logs are useless!
[Magisk] Setialpha:
yes

no

no

Some apps (like Pokemon Go) try to re-register themselves when the connection fails, but most don't.
[Magisk] Setialpha:
VDEX > ODEX and easier to de-odex, so if you see vdex files, ignore the odex files.
[Magisk] Setialpha:
nah, you either have

nanodroid_overlay=0

or

nanodroid_overlay=1

Though it likely works, aswell as aritmetically [0|1] != 0. And yes, it's the pseudo-debloat feature.

By default it will only debloat GApps if found, but nothing else, since the microG package doesn't offer alternative apps, so you need to tell it to debloat by having

nanodroid_overlay=1

in your nanodroid-setup file. And make sure the nanodroid-overlay configuration file only contains what you really want to get rid of.
[Magisk] Souvikhazra80:
Showing Error 1.:(
[Magisk] Setialpha:
Ok, hopefully fixed build, soon.
[Magisk] Setialpha:
Patcher 18.0~beta1+vdex_2

Find attached a second build which should fix ld issues on arm64 and x86_64.
[Magisk] tom.android:
error_log
[Magisk] Setialpha:
I see, as I thought baksmali code is not yet complete/error prove, could you please upload the full /system/framework folder somewhere? Thanks.
[Magisk] AndroidBeginNinja:
Hey man this is how you fix the playstore has the incorrect signature error I get this from shadow53

---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------

su

pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE

Do this within termux
[Magisk] tom.android:
Here my framework. > https://mega.nz/#!VHRAFaJS!TQWSNNZW-1bjatYaECgoPUIKap-wUBq2PfjZUv_Vd3s
[Magisk] Souvikhazra80:
This?
[Magisk] Setialpha:
Nope, I actually meant tom.android. did you try the second build?
[Magisk] Setialpha:
Thanks, I'll do some tests later today.
[Magisk] ska7:
not working . error 1
[Magisk] Setialpha:
Hmm... vdexExtractor doesn't create any output on your device. I'll make a new build with more verbose output, so the logs contain more information, later today.
[Magisk] ska7:
alright, thanks man
[Magisk] Souvikhazra80:
Ya,Same error.Changed. ROM to O,using closed fake gapps module now.:(
[Magisk] Setialpha:
Patcher 18.0~beta1+vdex_3

Another beta for the Patcher which tries to auto-deodex your services.jar:

verbose output from all tools, so your recovery.log contains more useful information

updated smali/baksmali builds

updated vdexExtractor builds

minor internal changes

use internal busybox for higher ROM compatibility

Android 9.0 is currently marked as experimental, as support for VDEX 019, respectively ODEX 039 formats is work-in-progress, across all used tools (vdexExtractor, smali/baksmali and dexpatcher).

Freel free to test and report back.
[Magisk] HyperCriSiS:
Can full package name be used to debloat?
[Magisk] Setialpha:
No, the directory name is required. Full documentation is here.
[Magisk] aaz03:
Latest vdex3 patcher not working for me on android Pie ( device Redmi Note 3 Kenzo on PixelExperience nontreble rom)

See recovery.log attached
[Magisk] ska7:
still showing error 1,

im using mcaosp PIE

device REDMI 5 PLUS
[Magisk] starbright_:
I have tested ..vdex und vdex_3.zip on a Galaxy A3 (2017)

I did this as sideload in TWRP, directly after installing LOS15.1 (arm32) and Magisk16.zip without any boot inbetween. (Is this an issue?)

Both trials fail.

It detects SDK27 and arm and a vdexed ROM

...

>>patching services.jar

!! failed to apply patches

Updates end with error: 1

But I am happy you try this to give also us the chance to spoof the ROM. Thank you
[Magisk] Setialpha:
You'll have to wait until the tools are updated for full Pie support. They choke on the VDEX 019 file format.

What's the log?
[Magisk] pavanmaverick:
v3 not working...

Just tried the latest patcher (beta v3), on Lineage OS 16, Pixel. Doesn't seem to work. In TWRP (v 3.2.3-0), I get the following error message:

deodexing services.jar [VDEX]
!! failed to deodex services.vdex
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/TWRP/NanoDroid-patcher-18.0_beta1+vdex+3.zip'

Same thing happens whether I've previously installed Magisk, or if I try without Magisk installed. Any advice on what to try differently? Recovery log attached (for beta v3).

Thanks.
[Magisk] pavanmaverick:
vdexExtractor?

If someone would post the latest vdexExtractor here, I'm happy to try manually deodexing Lineage 16 to see if the patcher will work.

Thanks.
[Magisk] HemanthJabalpuri:
Sir using internal busybox also gives error 1 in TWRP

ROM Stock Touchwiz 4.4.2
[Magisk] Setialpha:
Error 1 means nothing, except, that *something* happened, I need the log.
[Magisk] HemanthJabalpuri:
Attached above
[Magisk] aaz03:
here, freshly compiled (remove .txt extension, i made it so i could upload on xda) but it looks like vdex extractor itself can't extract

Manually odexing gives an error for me , whether it's with vdexExtractor 0.50 (segfault) or 0.41(invalid header) , both can't extract
[Magisk] mischasworld:
v3 patcher is working here with lg g4 h815 Lineage unofficial.

But it took ages to patch :) ~ 15 minutes
[Magisk] pavanmaverick:
Thanks! This needs to be run on a Linux machine, right?
[Magisk] aaz03:
I compiled for my machine so i suppose
[Magisk] kurtn:
Yes, patching Oreo takes significantly longer than nougat. Even in not odexed ROMs.
[Magisk] aaz03:
Wow, so , by chance my rom has both .odex and .vdex files and by deodexing on .odex file i could get to enable the signature spoofing. But patching with beta1 took time (~10min)
[Magisk] starbright_:
I am sorry, don't know how to create a log in TWRP?
[Magisk] tom.android:
New error-log for NanoDroid-patcher-18.0_beta1+vdex_3.zip
[Magisk] starbright_:
How did you create the log in TWRP (and get it out from there)?
[Magisk] aaz03:
Well, it looks like Phonesky play store can't spoof signature, it keeps FCing
[Magisk] pavanmaverick:
When I run the vdexExtractor (I only removed the .txt extension. Was I supposed to change the extension to something else?) on my machine (Ubuntu 18.0.4.1 LTS), it says "command not found." And yes, I have the executable flag ticked on for vdexExtractor.

Any suggestions?

Thanks.
[Magisk] aaz03:
Put it in a folder and access it from this folder doing folder/vdexExtractor -i ...etc
[Magisk] tom.android:
By in TWRP---Advanced---Copy log

Then goto your internal storage get the log there.
[Magisk] Setialpha:
Thanks for all the logs, I'll dig through them the next days.

Please don't post further logs, if you're on Pie, the issues currently can't be solved.

Of you're on ROMs older than Pie, feel free to continue testing.

Attached find a new build with more changes. Most noticeably: if services.jar already contains a classes.dex, deodexing process will be skipped, and improved baksmali invocation.

And yes, patching can take from 5 to 15 Minutes, depending on Android version and device's power. That's not a bug, just the way it is.
[Magisk] aaz03:
Hm... I can't grant spoofing permission
[Magisk] Setialpha:
It is auto granted when manually patched, not part of the permission model. See the microG self check.

Also you're not root, so it won't do anything in first place.
[Magisk] aaz03:
First attempt i forgot to do "su" look at the second time i execute the "npem"

Microg selfcheck says that playstore can't spoof

npem says
[Magisk] tom.android:
Can/t downloaded NanoDroid-patcher-18.0~beta1+vdex_4.zip
[Magisk] Setialpha:
You can't use npem to grant the permission on a self-patched ROM, as I said. What Play Store do you have installed? Fake Store, NanoDroid Play Store or officiall? If you had the officiall Play Store installed before, go to Settings > Apps > Play Store > 3-dot-menu > Uninstall Updates, reboot and check what happens then.

If it still does not work, only a logcat will help, to see what's wrong.

re-uploaded it, seemed to be a bad uploaded before, works now on my end.
[Magisk] tom.android:
error-log-test4
[Magisk] pavanmaverick:
I get an invalid attachment error message when I click on the file.

Oops. Never mind. Fixed now!
[Magisk] ska7:
did you have anything install? like magisk or any apps? or clean flash?
[Magisk] aaz03:
I've installed official Play store, did the uninstall updates and rebooted but same story. Although by replacing store with Yalp + Fake store everything works great