yashsingh1/xdaforums huggingface dataset:
[Magisk] Oswald Boelcke:
Yesterday, updated PS via Terminal Emulator by use of 'nupd ps' as root. No problem at all.

Did you first type 'su', followed by use 'nupd ps' afterwards?
[Magisk] Apex Predator:
Yes I did. Also tried in terminal emulator, same result. I searched the thread for this and got nothing useful other than it possibly being related to busybox. I run Stericson's BB, latest version, installed to system/bin.
[Magisk] Oswald Boelcke:
I used Stericson's BB long time ago i.e. currently no own experiences anymore. At the moment, running the Magisk module "Busybox for Android NDK" by @osm0sis (https://xdaforums.com/showthread.php?t=2239421) with great satisfaction. Consider to try this one, and to check if it's BB related.
[Magisk] Apex Predator:
Okay so I switched Stericson's BB for this osm0sis one but the update still doesn't work. There is some progress though as the output now includes IP addresses.

Updating: Phonesky

Connecting to www.nanolx.org (xx.xxx.xx.x:xxx)

wget: can't connect to remote host : (xx.xxx.xx.x:xxx) Connection refused

!! failed to download Phonesky

1|trlte:/data/data/com.termux/files/home #

I redacted the IPs just in case Setialpha doesn't like them bandied about here.

BTW when I switched BB, after the reboot Nanodroid seemed to have been wiped away. In addition, all the other system apps I had debloated with Magisk debloater were back. I guess something about the switch wreaked minor havoc.

Reinstalled Nanodroid, which thankfully detected Magisk this time and all is well again. Well, except for still not being able to update the PS.

Edit: success! This time I tried with terminal emulator, just for something different... And it worked! No idea why it didn't in Termux.
[Magisk] Oswald Boelcke:
@Apex Predator: Switched to Termux meanwhile. After your post, I tried to update PS again, and it succesfully went through. Please refer to screenshot.

I'm now more and more convinced that the issue rests with your device. Firewall? Adaway? Pi-hole? Whatwever blocks connection to the server...
[Magisk] Apex Predator:
Ha, there was never any doubt about that! To many configurables too keep track of...

All relevant apps have permissions in AFWall. I even disabled it completely for one test.

Hadn't considered Ad-Away though. I tend to only think of it in terms of browsers/apps etc, flashy places that display ads. Why would Setialpha's site be on any of it's lists? Either way I've added www.nanolx.org to it's whitelist.

Hopefully all this sticks and next update works properly. At least it's done for now.
[Magisk] Oswald Boelcke:
In regard to µG and especially GCM, a lot of people don't think about Adaway despite it's expressively mentioned in the OP of Marvin's microG thread:
[Magisk] Apex Predator:
Good tip, cheers. I've added it to the whitelist. I only use one app that needs push messages, and that seems to have worked fine so far anyway.

Actually I just had to uninstall then reinstall it due to having to reinstall Nanodroid. Push messages don't work when MicroG isn't present first.
[Magisk] Rbqttp:
Does micro-g support Google play games app ?
[Magisk] Oswald Boelcke:
An in-thread search with the powerful xda search engine provides quite a lot of respective answers:

https://xdaforums.com/search/thread/3584928?query=google play games

The µG implemenation status that is linked at quite a few sites (like this one) also provides the answer.

TL;DR: NO.
[Magisk] kindlyoldbear:
[MODULE/SYSTEM] NanoDroid 17.2.20180714 (microG, pseudo-debloat, F-Droid + apps)

Dumb question of the day: First time updating my rom since installing ND. Is the automatic patcher going to detect and do its thing in the background, or do I need to do something?

Edit: turns out I just needed to reflash magisk and the rest happens automatically.
[Magisk] sxml2015:
@ tom.android

Sorry for my English, google

Mi4c miui10 odex

I tried not to succeed

The video is broken. Beginners want to see

Can you use this?

https://xdaforums.com/android/software-hacking/tooll-03-12-fulmics-deodexer-1-0-t3512081
[Magisk] Oswald Boelcke:
Please repeat in English in order to allow everybody to benefit from your valuable input.
[Magisk] CoLdIcE42:
Hi,

i am running official LOS 15.1 in my rn5 . This Rom is deodexed so I cant use the patcher provided by nanodroid however I flashed the micoG package and activated the fake GApps xposed module and microG is showing Signature spoofing enabled however I cant install or remove apps because the apk installer keeps crashing and Playstore installed with microG too

Can I fix this somehow so I dont have to mess with odex ?

Thanks in advance
[Magisk] Oswald Boelcke:
If your ROM is deodexed the Nanodroid patcher should work; it doesn't with odexed ROMs.

Did you give the patcher a try?
[Magisk] CoLdIcE42:
Oh Im sorry I mean odexed of course because I gave the patcher a try and it failed because of odexed ROM.

Its just that It seems like microG is working fine however other system apps like the apk installer crash. When I remove microG everything is working fine again.
[Magisk] d1n0x:
If there is official LOS for your device, why not just use official lineage microg build? download.lineage.microg.org
[Magisk] kurtn:
Im my case installer crash always was magisk issue. But maybe in your case its caused by xposed. Easy solution: take a different ROM or a different root method.
[Magisk] CoLdIcE42:
Thanks for the hint I will consider it
[Magisk] clewis.it:
Go to Settings > Apps & Notifications > See all ## apps.

Tap the 3-dot menu button and select Show system.

Tap Google Play Store

Tap Storage

Clear cache

Go back to the app list

Tap Package Installer

Tap storage

Clear cache and data

Reboot.
[Magisk] inVain_theGenuine:
in the past, rebooting my device has solved this issue for me ;)
[Magisk] CoLdIcE42:
This solved the issue big thanks !

However apps are unable to register (even after checkin) and I am not able to use the fake appstore login provided by yalp store . I guess I will have to flash the dedicated Rom .

Thanks for helping me guys
[Magisk] Setialpha:
Uploaded modified PlayStore 10.8.50, use 'nupd ps' as root, on-device, to update.
[Magisk] Setialpha:
17.3

Hi all, version 17.3 is now available.

What's new?

further improved GApps removal mechanism (permission handling)

ensure value of NANODROID_UPGRADE is programatically correct

fix issues with Google Play and microG GmsCore due to non-whitelisted priv-app permissions, most noticeable crashes and failing app installations in Google Play

usual updates

Addtional Note

You may have to clear cache/dalvik-cache, as well as Google Play data to make the changes take effect,

if you're not on a clean installation.

Also it seems Google Play now requires all four standard-permissions (Phone, Contacts, Storage, SMS) to be granted, else it won't properly work it seems!?

Full ChangeLog

## 17.3.20180730

### Bug Fixes

* CommonInstaller
* improve permissions-resetting during GApps removal
* now ensured to be only triggered on fresh NanoDroid installations
* Full, microG packages
* fix Google Play issues due to missing privapp-whitelisted permissions
* likewise for microG GmsCore

### Updates

* automatic
* Substratum (999)
* (Simple) Gallery (4.4.0)
* OpenKeychain (5.2)
* QKSMS (3.4.2)
* NewPipe (0.13.7)
* F-Droid (1.3-alpha5)
* KeePass DX (2.5.0.0beta15-libre)
* (Simple) Calendar (4.1.2)
* Face Slim (3.4.0)

* manual
* Google Play (10.5.80)

Download links

Download from AFH or Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] tom.android:
Howto Prevent The Play Store From Updating Itself.?
[Magisk] YamiYukiSenpai:
After updating NanoDroid, YouTube Vanced stopped working on my Moto Z (Resurrection Remix 6.1.0), while my Galaxy S4 (Resurrection Remix 5.8.5) is perfectly fine

I cleared YouTube Vanced's data, removed and reinstalled it. Nothing worked. I also reinstalled NanoDroid.

Anyone else experienced this?

Edit: NanoDroid stopped working
[Magisk] Oswald Boelcke:
Use a tool like "MyAndroidTools" (I clearly suggest the pro-version) and disable following service in Google PS: DailyHygiene$DailyHygieneService

How did you manage signature spoofing in the Moto Z with RR-O-v6.1.0? At least your screenshot shows that it isn't available for the Play Store.
[Magisk] YamiYukiSenpai:
Didn't do anything special. I thought it was always there. Before the update, everything was running fine.
[Magisk] Oswald Boelcke:
By my information all Oreo are odexed. Nanodroid patcher only works with deodexed ROMs. Either find a ROM for your device that is inherently signature spoofing / "ready for µG" (e.g. LOS for µG) or follow @Setialpha's advice here.
[Magisk] YamiYukiSenpai:
Found the reason why it wasn't working

The Play Store's spoofing got "deactivated" after the update
[Magisk] abacate123:
As said, you can also install Xposed (for your specific Android version, obviously), and this module, it'll work flawlessly. Too bad you won't be able to pass safetynet anymore with Xposed, but well, not a big deal, at least things will work as it should :)
[Magisk] Setialpha:
17.4

Hi all, version 17.4 is now available.

I've found a stupid Typo in the CommonInstaller which caused the permission losses during upgrades in Magisk Mode installation. It's fixed now.

So if everything is setup fine before the upgrade to 17.4 it will stay like that. But if you've had troubles before (caused by 17.2 or 17.3) and haven't fixed them already, then issue the following steps to get rid of those:

remove Google Account

reboot to TWRP and clear cache/dalvik-cache

check setup of microG (Settings + Permissions)

check setup of Play Store (Permissions)

re-add Google Account

et voila

sorry for the trouble.

ChangeLog

## 17.4.20180731

### Bug Fixes

* CommonInstaller
* fixed a bug that caused NANODROID_UPGRADE to be wrongly set to 0
* causing issues with permissions for Play Store and microG GmsCore

### Updates

* automatic
* Google Play (11.0.20)

Download links

Download from AFH or Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] isaactsg:
Error installing >= 17.2

Trying to install any Nanodroid > 17.2 Beta (17.2, 17.3, 17.4) results in the error: failed to mount /system (unsupported A/B device?).

It's a Xiaomi Mi A1 Running CrDroid 8.1. I've tried with both Magisk 16.0 and 16.7, after both wiping system and dirty flashing over a working Nanodroid.

I have attached the recovery.log file.

Right now I'm just sticking with 17.2 Beta1.
[Magisk] clarkcant:
Would I need to deodex my ROM in order for that to work?
[Magisk] kurtn:
Deodex is only to be able to patch spoofing. There are easier methods

https://xdaforums.com/android/general/index-list-custom-roms-offering-t3557047
[Magisk] Setialpha:
17.5

Hi, following the Google-advice "release often. early" (hah! as we would follow any Google-advice), version 17.5 is now available.

What's new?

fixed installation from TWRP with Magisk 16.6 or newer when the device never booted into ROM once

fixed logical error in supporting devices with A/B partition scheme (so it possibly works again)

updated microG GmsCore (spoofs Play Services Version 12.8.74), MPV and Google Play

updated and improved a few parts of the documentation in the git repository

Full ChangeLog

## 17.5.20180803

### Bug Fixes

* CommonInstaller
* fixed installation from TWRP with Magisk 16.6 (or newer) if device was never booted into ROM once
* (possibly) fixed support for devices with A/B partition scheme

### Updates

* automatic
* (Simple) Gallery (4.4.1)

* manual
* microG GmsCore (0.2.4-127)
* bumps spoofed Play Services Version to 12.8.74
* mpv (20180802)
* new upstream snapshot
* Google Play (11.0.50)

Download links

Download from AFH or Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] apollo3x:
Hi, i installed the latest stable build.

My rom is microg ready but contact sync is not present. I ticked them in aroma installer. Calender is getting synced but contacts are not. Any help would be appreciated! :)
[Magisk] abacate123:
It's fine here.
[Magisk] Setialpha:
Uploaded modified Play Store 11.1.15, use 'nupd ps' as root, on-device, to update.
[Magisk] bertino:
Make sure you have all permissions for google contacts sync app and google backup transport (system) apps.
[Magisk] abacate123:
[MENTION=4187311]Setialpha[/MENTION], can you tell me how did you fix it? Or lead me to the GitLab commit. Facing the same issue with some other modules. Thanks.
[Magisk] Setialpha:
... I'm doing the whole thing in something a non-standard way, so feel free to check if you can make use of it.

Git Commit
[Magisk] apollo3x:
Thankyou! Permissions were missing! I've granted them! Let's see

Also, can you help me with location?
[Magisk] mtkmanjaro:
I'm on crdroid adroid 8.1, but nanopatcher fail with error 1 odexe roms are no supported Wtf my rom is no odex

Any suggestions
[Magisk] tom.android:
crdroid is support signature spoofing. you don't install nanodroid patcher just installed nanodroid in normal way then find setting---permission ----> enable signature spoofing and another permission their.
[Magisk] Kajuru:
Can you consider making the setupwizard reload the set options from the file instead of reverting to default everytime you enter it? Having to (un)tick everything again just because you want to try one single change is a pain.
[Magisk] Setialpha:
I doubt it's technically possible at all, as AROMA reads the config file as-is and thus can't load anything from outside.

Either way, you can always edit the files manually, everything described in the doc.
[Magisk] apollo3x:
I can't get geolocation to work! Everything else is working ! Any help would be appreciated
[Magisk] sxml2015:
I'm sorry! Google translation

Tingle does not support ODEX. Don't understand how to operate forcesystem and sigspoofui?

Can you put it in detail again? Thank you! [MENTION=5994172]digitman xxx[/MENTION]

MIUI odexe
[Magisk] Setialpha:
17.6.20180805

Hi all, yet another bug fix release is now available: 17.6.

What's new?

the upgrade-detection mechanism now properly works when upgrading from Magisk Manager, too

fixed A/B partition scheme support (confirmed working)

fixed issues with GSync adapters installation (System Mode)

ChangeLog

## 17.6.20180805

### Bug Fixes

* CommonInstaller
* fix creating uninstaller information for GSync adapters (System Mode)
* fix permission setting for GSync adapters (System Mode effected)
* fix for A/B partition scheme support
* fix for upgrade-detection mechanism when upgrading from Magisk Manager

Download links

Download from AFH or Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] sxml2015:
[MENTION=7586138]tom.android[/MENTION] Request video! Thank you!
[Magisk] tom.android:
Please upload your framework folder and build.pro.

But if you use chinese rom such as MIUI china ROM ,you will found that UnifiedNlp is not registered in system, the best way for you is use xposed (fakeGapps + XposedGmsCoreUnifiedNlp) that can't pass safetynet check.
[Magisk] raptorddd:
i am on miui 10. oreo so cant patch.. or cant use fakegapps as xposed bootloops.

is there a magisk module?
[Magisk] tom.android:
we can't deodex oreo 8.1.
[Magisk] mtkmanjaro:
Danms i forgot that Crdroid RR etc, support signature spoofing

Thanks mate
[Magisk] raptorddd:
i know am on 8.1 miui.

so cant patch, nor use xposed for fakegapps.. since i started using magisk thats what i asked if there was a magisk module that allow me signature spoof.
[Magisk] Setialpha:
Nope, Xposed would be the only way, Magisk does no patching at all, unlike Xposed.

Alternatively use a pre-patched ROM, there are many now.
[Magisk] mdl054:
Not true, Super R's kitchen can do it. https://xdaforums.com/apps/superr-kitchen/windows-linux-superr-s-kitchen-v3-0-0-0-t3601702 :highfive:
[Magisk] inVain_theGenuine:
there's systemless xposed by john wu, himself:

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268
[Magisk] sxml2015:
[MENTION=7586138]tom.android[/MENTION]

Sorry! Google Translate.

Is your video still there? I tried the microg didn't change, I want to see the video and try again.

Microg I only need Google Cloud Messaging, other features don't.

mi4c MIUI10 china ROM Android 7.0

framework+ build.pro

https://mega.nz/#!SR9y0aYA!FAtwPej96hK68SMdLm4N5XVGoBSjwrrQwoqnlb2-r3c
[Magisk] tom.android:
This is your file (Magisk module) for add with Magisk Manager or flash with TWRP.

New(Signature_spoofing_Patcher-mi4c-miui-10-CN-8.8.6.zip)

Download: https://mega.nz/#!RagwhSga!hIo-_JR7ncwbWEE3alxPdr1KBeIsU-CWGAleASW6FYU
[Magisk] Setialpha:
Uploaded modified Play Store 11.2.15, use 'nupd ps' as root, on-device to update.

Clear app data and re-grant it's permissions if it doesn't properly work after the update.
[Magisk] CoLdIcE42:
Hi,

sorry for the noob question but where exactly should I use 'nupd ps' as root ?

Thanks in advance.
[Magisk] tom.android:
install busybox module first and ......
[Magisk] temporarium:
My install appears to be correct; passes all checks. But I don't have anything in these two screens. Am I the only one? Why would this be? Is it correct?
[Magisk] jenslody:
The first (on third picture) is normal, it's just not implemented, the second (forth picture) is normal if no apps have registered for gcm.

The apps have to be installed after microG is setup, otherwise they will not register. In most cases it's enough to clear the apps data in settings, force close and restart it.

Some newe apps do not use gcm, but firebase messaging (e.g. threema and slack). For those apps it can work, if you install an older version of the apk first and update it after the first run (this works for threema and slack).
[Magisk] sxml2015:
[MENTION=7586138]tom.android[/MENTION]

thank you! thank you very much! thank! ! !

Magisk put a patch, happy!

Where was my mistake? Can you teach me?
[Magisk] tom.android:
You're welcome.!!!!! Nanodroid is always the best.
[Magisk] tullian:
Termux shows me this, and the phone makes a very unhealthy noise like it was trying to vibrate but couldn't manage.
[Magisk] tom.android:
cause you don't installed busybox first
[Magisk] Setialpha:
I guess he did install *a* busybox, but I assume not the one from [MENTION=4544860]osm0sis[/MENTION] - I've already seen this faulty behaviour from other/old busyboxes with non-standard/buggy wget implementations (on Android non-osm0sis busyboxes should be forbidden, they cause trouble way too often).

Or worse: it may be toybox or similat in disguise (brrrrrr~~~)

The wget on his device streams to stdout instead of the requested output file, thus this shell bells (= 'unhealthy noise'), it's harmless, don't worry.
[Magisk] Setialpha:
Depends on the dex version: smali/baksmali only supports dex version until 036 or 037, Android 8/8.1 introduced newer versions.

Some Oreo ROMs (mostly aftermarket) use older dex format, others (mostly stock) use the newest, unsupported format.

So it may or may not work.
[Magisk] tullian:
Well, what can I say... I had not installed any Busybox, let alone the right one. :o How the heck could I miss that?

Thanks guys!
[Magisk] temporarium:
Most of my apps were restored via Titanium, so not installed post-microG. I'll play around with these and see if they start populating that field ??
[Magisk] gadgetguy08:
Attempting to use framework-patcher on Essential PH-1 (A/B device) with Oreo 8.1. Connected with TWRP (although it is a bit specialized for the device).

Get these messages:

/home/owner/Downloads/framework-patche...ushed. 1.2 MB/s (4056 bytes in 0.003s)

/tmp/framework-patcher-remote: line 173: grep_cmdline: not found

/tmp/framework-patcher-remote: line 173: grep_cmdline: not found

mount: mounting /dev/block/platform/soc/1da4000.ufshc/by-name/system on /system failed: Device or resource busy

Failed to install /system

I also tried the patcher zip, but got ERROR1 with a comment [unsupported A/B Device?] Failed to mount system.

Probably just go manual.
[Magisk] kurtn:
If you have solved all other problems, you still have an odexed ROM that can not be patched with the available tools. Nanomod patcher normally has a good to read message in twrp display about that.
[Magisk] Setialpha:
The Patcher does not mount A/B properly yet, wait for 17.7, and that's what the error message is about. Anyway the patcher only supports deodexed ROMs, starting with 8.1 basically all are odexed, so it won't work (yet) anyway.
[Magisk] CoLdIcE42:
I had the same issue. A playstore busybox app wont do the trick you will have to install the busybox magisk module.
[Magisk] gadgetguy08:
Thanks for the replies.

I wasn't as clear in my question as I should have been: the ROM is a deodexed version of the 8.1 stock.
[Magisk] utg1:
Sorry guys, I'm a bit confused: now safety net works or not with new NanoDroid?
[Magisk] tom.android:
Working!
[Magisk] utg1:
Thanks!

Like you I have Miui 10: have I to install also your signature spoofing Magisk module ?

I have a Markw device (RedMi 4 Prime).
[Magisk] mdl054:
edit* redundant sorry
[Magisk] Setialpha:
17.7.20180809

Hi all, version 17.7 is now available.

What's new?

A/B partition scheme support in Patcher, Uninstaller and extra scripts

improved nanodroid-upd script

fixed upgrade-detection for System Mode

Note: it's late and I'm lazy, so currently only uploaded to Nanolx, AFH will follow tomorrow.

Full ChangeLog

## 17.7.20180809

### Bug Fixes

* CommonPatcher
* fix for A/B partition scheme support
* Uninstaller
* fix for A/B partition scheme support
* CommonInstaller
* fix upgrade-detection for System Mode
* NanoDroid-Upgrade (nanodroid-upd)
* improve check for proper wget implementation

### General Changes

* force-debloat.sh
* support A/B partition scheme
* on-pc framework-patcher
* support A/B partition scheme
* Full package
* remove Lock/Unlock sounds
* NanoDroid-Upgrade (nanodroid-upd)
* add `mg`, `microG` parameter to update microG GmsCore custom build
* add `dg`, `DroidGuard` parameter to update microG DroidGuard Helper custom build
* remove `bt`, `Bucket` parameter as it no longer supported

### Updates

* automatic
* (Simple) Calendar (4.1.3)
* F-Droid (1.3)

* manual
* Play Store (11.2.14)
* MPV (20180806)
* GNU Bash (4.4.23)

Download links

Download from Nanolx.

Bug reporting

In case of errors, please provide

/data/adb/MODID_log_INSTALLDATE

/data/adb/MODID_twrp_INSTALLDATE (TWRP Installation)

logcat (if applicable)
[Magisk] sxml2015:
NanoDroid-microG-17.7.20180805

How to upgrade 0809?

Magisk direct installation coverage?

Need to uninstall the 0805 upgrade?