yashsingh1/xdaforums huggingface dataset:
[Magisk] gadgetguy08:
Tried the zip and the framework-patcher from Linux laptop.

failed to mount /system (unsupported A/B device?)
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/NanoDroid-patcher-17.7.20180809.zip'
Updating partition details ...
Failed to mount '/system' (Device or resource busy)
...done

Cloning into 'haystack'...
remote: Counting objects: 443, done.
remote: Total 443 (delta 0), reused 0 (delta 0), pack-reused 443
Receiving objects: 100% (443/443), 213.70 MiB | 1.75 MiB/s, done.
Resolving deltas: 100% (163/163), done.
Checking connectivity... done.
/home/owner/Downloads/NanoDroid-master/framework-patcher-remote: 1 file pushed. 1.4 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/bootdevice/by-name/system_a on /system failed: Device or resource busy
mount: mounting /dev/block/platform/soc/1da4000.ufshc/by-name/system on /system failed: Device or resource busy
/tmp/framework-patcher-remote: line 173: error: not found
/tmp/framework-patcher-remote: line 173: error: not found
Failed to install /system

It didn't get far enough to create the adb folder.

This A/B system (and perhaps true for all) doesn't have a recovery partition per se. TWRP gets loaded into the boot partition. Then I can push the boot.img and Magisk to root, but I cannot reboot without losing TWRP. I wonder if I am truly rooted at this point. Using TWRP File Manager, I am unable to select System to mount manually in TWRP except in read-only.

If I install TWRP in the other slot, it doesn't allow a clean change back to the primary to flash.

Would there be a way to run the patcher from the laptop using ADB without being in TWRP?

UPDATE: I can now push a patched boot img file with root so this isn't the issue.

Now when I flash the patcher.zip it starts to deal with the jar file (for 30 seconds or so) and then starts looping TWRP.

If I execute the script I get this:

Already up-to-date.
/home/owner/Downloads/NanoDroid-master/framework-patcher-remote: 1 file pushed. 0.9 MB/s (4056 bytes in 0.004s)
/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
[Magisk] tom.android:
No you don't want to install my cn-miui signature spoofing patch.
[Magisk] inVain_theGenuine:
excuse me for the lame question, but;

where can I find the "/Magisk" partition which contains the magisk modules on a LOS 15.1 treble rom?

I did found magisk.img and /magisk on /data/adb, but I couldn't find the installed modules like when I was on a non treble rom.

I used to install my 3rd party apps (non Nanodroid) as a system app by simply extracting its libs file and copy them to the /Magisk partition.

I also used to rename every conflicting functions between: Toybox & osm0sis Busybox by simply renaming the conflicting functions.

So, being unable to look for the mounted /Magisk partition really frustates me.
[Magisk] Didgeridoohan:
The Magisk image mount point is /sbin/.core/img. It hasn't been /magisk since Magisk v14.5, but there's been a backwards compatibility symlink to /magisk up until Magisk v16.3.
[Magisk] sxml2015:
upgrade

Apps using Google Cloud Messaging

Registered apps, all disappear
[Magisk] tom.android:
If you used NanoDroid-setupwizard and kept pre-configuration file (.nanodroid-apps,.nanodroid-overlay,.nanodroid-setup) , it easy to update version just flash or use magisk manager add NanoDroid-update-version.zip.
[Magisk] inVain_theGenuine:
thank you very much!

you've made my day :)
[Magisk] maybeme2:
I have some newbie questions.

I am currently on lineageos 14.1 with microG (Yalp but no Google play store) and am unhappy because even though lineageos updates regularly, the microG version has not in a long time and I need to extract and update it manually from noGooLag.

I read that Nanodroid might offer a more convenient alternative.

Is that so? Does the Nanodroid offer regular updates to microG so that apps don't complain that I need to update 'Google play services' form the app to work?

If so, what exactly do I need to do to switch to Nanodroid?

How is the Nanodroid fork different?
[Magisk] finnal123:
I cant watch youtube now. What version of youtube i should use now?
[Magisk] gadgetguy08:
[MENTION=4187311]Setialpha[/MENTION]

Finally got things sorted. Not sure what was the root cause, but TWRP is a bit wonky on this device.

I ended up using Tingle patcher in Manual mode since there were issues with that in automatic mode on this ROM as well.

Thanks for Nanodroid and being so quick to respond!
[Magisk] sxml2015:
thank you!

Where can I download this? Can't find

NanoDroid-update-version
[Magisk] Setialpha:
update-version is just a placeholder for the latest Version, eg. NanoDroid-17.7-20180809.zip, just download the lastest version and flash it.

I don't know, I don't use the official YT app. Also what does "not work" mean?

But did you grant all permissions to Play Store / microG GmsCore? If not, that's likely the cause. Personally I use NewPipe as a YT frontend.
[Magisk] Setialpha:
Thanks, I've spotted two issues in the framework-patcher script. You may try again. For the Patcher Zip I'd need the /tmp/recovery.log file to have a better look at the issue.
[Magisk] Setialpha:
Well everything you need to know is in the full documentation. tl;dr NanoDroid has a full package (with *lots* of extra stuff), aswell as small microG and FDroid packages. All packages are modular to a certain degree, so you can choose whether to have FakeStore only, Yalp + Fake, or modified official Play Store (modified means you can make purchases with my modified version) or which nlp backends, see the "Alter Installation" section and/or the SetupWizard. I'm regurarly updating (see the ChangeLog), plus there's also a script which (nanodroid-upd) you can use on the device to update any of my self-built apks (currently: Fake Store, MPV, microG GmsCore, DroidGuard Helper and Play Store), if I drop an update (which is announced in this thread). NanoDroid further supports both system mode installation (with addon.d) and installation as a Magisk module, aswell as devices with A/B partition scheme.

The documentation might be huge at first, but gets you covered.
[Magisk] Setialpha:
The next version, 17.8 will fix A/B partition scheme support in pc scripts, fix the issue that Play Store looses some granted permissions during update and adds two new fonts to choose from.
[Magisk] inVain_theGenuine:
I've just tried the the microG version of LOS 15.1, and I really want to go back to Nanodroid straight away :D

Nanodroid gives us option to choose between: patched playstore, yalp, or no store (fake store) at all.

The patched playstore, so it can be used to purchase apps with microG is a unique feature to Nanodroid.

Nanodroid also contains the patched version of microG (or is it the droid guard?) so we can pass the safetynet with microG.

The patched playstore got regular updates, or frequently updated I'd rather say; thanks to Setialpha.

But as with microG, its update is really depend to the microG project itself. Nanodroid just made life easier for people who would like to move away from google since it's bundling everything we need....

but heck, it's still useful even for people with google as well.

From experience (yes, I did try the forked LOS 14.1 with microG as well) I'd rather go with the official LOS 14.1; patch its service jar with the Nanodroid Patcher and then install the Nanodroid Package.

It can be quite a headache at first, but somehow I get by. Just make sure to read the documentation first, and don't omit the setup wizard if you're doing it the first time.

Nanodroid also allow us to modify system apps sytemlessly, a feat which I found it is really hard to live without (at least without the slimroms around).
[Magisk] tom.android:
Delete ....cause out of date
[Magisk] joey118:
can i flash this on lineage os 15.1 ?? i dont have magisk only supersu
[Magisk] abacate123:
As you can see on the title "module/system" and in the documentation (as I'd guess you didn't even read it), yes, you can use this mod with or without magisk, it'll detected there's no magisk, then it'll install directly to system, automatically.
[Magisk] Setialpha:
17.8.20180811

Hi all, version 17.8 is now available.

What's new?

A/B partiton scheme fixes for PC scripts

improved GApps removal mechanism (fixes Play Store loosing permissions after upgrade)

two new fonts to choose from

Credits section in the documentation now features weblinks

ChangeLog

## 17.8.20180811

### Bug Fixes

* CommonInstaller
* improve GApps removal mechanism (most noticable: fix Play Store data loss during upgrade)
* CommonAddon
* improve GApps removal mechanism (most noticable: fix Play Store data loss during upgrade)
* force-debloat.sh
* fix support for A/B partition scheme
* on-pc framework-patcher
* fix support for A/B partition scheme

### General Changes

* NanoDroid-Font (nanodroid-font)
* add `Splatoon` and `SuperMarioOdyssey` fonts
* in Sytem Mode only backup original font, if the requested custom font exists
* README
* add weblinks in the Credits section

### Updates

* automatic
* F-Droid (1.3.1)
* QKSMS (3.4.4)
* KeePass DX (2.5.0.0beta17-libre)
* (Simple) Gallery (4.5.2)

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] Radamanti:
Hi people!

Sorry, I'm a neophyte of the world without b1g G.

I've a Nougat 7.1.2 system with manually installed MicroG Official 0.2.4.111 and relative apps.

To upgrade to the latest NanoDoroid via TWRP (simply flash the zip archive, right?) do I have to remove the older version? (actually installed as user app)

Registered GCM apps can disappear?

I already have a lot of problems with delayed whatsapp notifications, I would not make it worse.

Thanks for all and sorry for my english.
[Magisk] sxml2015:
[MENTION=4187311]Setialpha[/MENTION]

Magisk

Install the latest version of NanoDroid-microG-17.8.20180811.zip.

Google Cloud Messaging

All disappeared?

Very troublesome, the app needs to clear all the data before it can be re-registered.

Where is NanoDroid-update-version.zip?
[Magisk] joey118:
Already flashed through twrp and my twrp crash...Any solutions?

Currently running lineage os 15.1
[Magisk] abacate123:
Saying just "my twrp crash" and "currently running lineage os 15.1" won't help. Grab and give the recovery logs with the installation errors to the developer. So he'll be able to do something about it. Also, try to update your twrp and use (if possible) the official one, this may help in some cases.
[Magisk] Setialpha:
You should be able to just upgrade, Android will take whatever is newer.

If you don't boot without any microG GmsCore, you won't loose GCM registration, so if you first uninstall the current GmsCore, you'll definitively loose GCM registration, obviously.
[Magisk] Marc0601:
Hey guys, thx for this amazing work,

I am using v17.7 and i had installed setup wizzard first then nanodroid package

What is the best way to update nanodroid to latest version??

Can't u make an update system from the app, so not evry 2 days w re-download the new update??
[Magisk] Radamanti:
Thx's a lot! :)
[Magisk] abacate123:
Just flash it over the previous one, either through Magisk Manager (if you use it) or through TWRP. Unless if pointed out by the developer that a clean install is needed.
[Magisk] kmem:
I've been having a strange issue with the last several updates. Seems to occur with both magisk 16.0 and beta 16.7. Since about 17.1 I get error 1 when trying to update from a previous version of nanoDroid. This appears to be caused because the magisk image is being mounted in read only mode. The solution for me has been to uninstall and reinstall magisk and all associated modules including nanoDroid. This isn't ideal as it adds a lot of overhead to the upgrade process.

Is there anything that was changed around version 17 that might cause this mounting issue or has anyone else has had a similar issue? I searched the thread but came up dry.

I'm using an old version of TWRP which I suspect might add complexity but it hasn't been an issue pre 17.x

Thanks in advance.
[Magisk] temporarium:
I'm on the latest nanoDroid, with Push Notification Tester installed after nanoDroid. Still, it fails. Any suggestions/ideas?

And thank you for implementing privacy!
[Magisk] temporarium:
Screenshots
[Magisk] Marc0601:
Do I need to reflash setup wizzard of new version??

Or just flash nanodroid package through twrp

Also do i need to redo all stuffs again, sigin to Google... Etc ??
[Magisk] abacate123:
No, the setup wizard will generate the .nanodroid-setup file inside your internal storage, which is the file you need. If you let it there, you don't need to reflash the setup wizard.

No, you don't need to redo stuff. Unless if required explicitly.
[Magisk] nadastry:
On my Galaxy Tab S2 9.7 I used the Aroma installer.

It works, but the rotation is wrong.

TWRP on this device is in Landscape, the Aroma installer is in Landscape, but the touches of the Aroma installer are in Portrait.

So I have to touch as if it is in Portrait but the text is in Landscape.
[Magisk] temporarium:
Nevermind, I installed an app that asked to register for push notifications and showed up in the list.

I guess the Push Notification Tester doesn't diagnose correctly.
[Magisk] Apex Predator:
It uses Firebase now not GCM. MicroG doesn't support Firebase so it will always fail.
[Magisk] michaelnothing:
Question, has anyone tried getting pandora to work with a pandora headunit with microg? I have a pandora specific alpine stereo in my car, and, can only stream pandora through the Bluetooth source. Checked with a stock phone and it works flawlessly. I'm thinking since it depends on Google services it just doesn't like microg. Any ideas for work arounds? I would like to use the pandora controls rather than on my phone.
[Magisk] HyperCriSiS:
Also with newest NanoDroid the Installation does not work. S5 with newest TWRP. ROM is DotOS Oreo. When I start the setup wizard the aroma installer just freezes and recovery reboots. Does anybody have a clue what's the issue?

Thanks,

Hyper
[Magisk] Setialpha:
AROMA is an old, unsupported project, if it diesn't work, just create the configuration files on your own, as described in the documentation.

Also, just for the record: it's not the installation that fails, 'just' the creation of user defined configuration files.
[Magisk] finnal123:
It show message "google service not found". Installing lastest ver still not fix
[Magisk] Setialpha:
I guess you did not grant sigspoof permission to Play Store or microG is not properly setup.
[Magisk] massiveMasturbator:
Got logged out of YouTube vanced after flashing and can't sign in now
[Magisk] kmem:
Vanced is working fine here with latest rev.
[Magisk] Setialpha:
Uploaded modified Play Store 11.3.15, as always: use 'nupd ps' as root, to update.
[Magisk] d1n0x:
I am trying to flash the latest NanoDroid over the latest LOS MicroG fork, but after flashing, Play Store doesn't show up. I selected it in the setup wizard along with forcing a system installation. Everything else is there.

I also tried the standalone zip on Shadow's website, but it doesn't show up either.
[Magisk] daftect:
I have the same issue here. I just flashed the NanoDroid-microg with TWRP (it shows up on Magisk, so I guess I could've just used Magisk) and even tho my .nanodroid-setup has :

OnePlus5:/sdcard # grep play .nanodroid-setup

nanodroid_play=1

OnePlus5:/sdcard #​

Play Store doesn't show up. I use LineageOS 15.1 with MicroG builtin and only "upgrade" the microG with NanoDroid subpackage. It works just fine, even better than without it (because the version is higher, I guess), except the playstore doesn't show up.
[Magisk] Setialpha:
Full logcat please, I suppose it's some kind of conflict, and the packagemanager logs should sched light.
[Magisk] daftect:
At which point you want the logcat? When I install the .zip with Magisk? How does one access packagemanager's logs?
[Magisk] Setialpha:
Just a complete logcat from boot to the running system, it contains the packagemanager logs.
[Magisk] daftect:
Here it goes. I had issues with Signal, unrelated to all this. Anway, here it goes. First time I attach something here.
[Magisk] keon1:
I've installed this and every thing in the self check settings are checked, along with everything else. All permissions are given.

But i'm getting this google play services error on most apps.

Can somebody help?

Sorry, I'm new to this.

Pictures attached of (two) errors.
[Magisk] d1n0x:
Push notification tester uses FCM, which is not (yet?) supported by MicroG.
[Magisk] keon1:
Oh okay thanks.

Do I just need to update Google Play Services via Play Store to fix the error? Or is that not the right way to fix it?
[Magisk] d1n0x:
Why use Google Play Services when you use MicroG? It won't update anyway since the signature is different. There's nothing you can do other than wait for MicroG to implement FCM, which might take a long time if it ever happens.
[Magisk] keon1:
Okay thanks
[Magisk] kurtn:
The right way to fix android without GApps is using apps from f-droid. They don't need firebase or anything else from Google play services.
[Magisk] namanjr:
It's the preinstalled fakestore.apk conflicting. Once you remove that it works.
[Magisk] daftect:
And how do you suggest we properly fix this? I guess Setialpha will have to handle this case in the installer?
[Magisk] Oswald Boelcke:
Disagree.
[Magisk] Setialpha:
Yes, will be fixed in 17.9, see the git repo, it's already live, though untested yet.
[Magisk] daftect:
I checked it out and it looks like it'd do. Can't wait to see it released.
[Magisk] Setialpha:
17.9.20180818

Hi all, version 17.9 is now available.

What's new?

fixed System Mode installation in some cases caused by linking errors

improved App Store installation routine

when Play Store is installed, get rid of Fake Store

when Fake Store is installe get rid of Play Store

previously Yalp and Fake Store were always installed together, now you can choose between Yalp Store only or Yalp Store + Fake Store installation

new option to force installation of NanoDroid apps, even if the ROM already has them built in (off by default)

Full ChangeLog

## 17.9.20180818

### Bug Fixes

* CommonInstaller
* fix System Mode installation in several cases, caused by linking issues

### General Changes

* CommonInstaller
* value `2` for `nanodroid_play` will now only install Yalp Store
* value `3` for `nanodroid_play` will now check if Play Store is installed and will get rid of it in favour of Fake Store
* value `1` for `nanodroid_play` will now check if Fake Store is installed and will get rid of it in favour of Play Store
* simplify App Store installation routine
* CommonInstaller, SetupWizard
* new value `4` for `nanodroid_play`, will install Yalp Store and Fake Store
* new setting `nanodroid_override`, whether to override an existing app
* `0` means that a ROM app is preferred against a NanoDroid app, where `1` means the NanoDroid apps is prefered.

### Updates

* manual
* Play Store (11.3.15)

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] daftect:
I can see the Play Store now! However I get the dreaded RH-01 and no matter if I force close erase data I keep getting the error.
[Magisk] Setialpha:
Does it have sigspoof permission granted?
[Magisk] daftect:
Everything is checked in the Self Check.
[Magisk] D4ND310:
Reboot to Recovery and wipe Cache/Dalvic. That usually instantly fixes it for me.
[Magisk] d1n0x:
Reboot
[Magisk] daftect:
It's one of the things I tried. Anyway I started from scratch wipe and it works now.
[Magisk] HaoZeke:
?? I spoke too soon... It doesn't seem to do anything but spin. Ah well.
[Magisk] saturday_night:
I am so glad this project was/is made. Finaly i could get rid of all google stuff on my Phone. Tried this about a year ago but never was able to, but now with this magisk module in combination of flashable signature spoofing and fake store it worked. With fake store i also can use my paid apps from google play store. Only for updating my paid apps i made a small installation of slimrom with the minimum installation only play store+services+my paid apps + apk extractor. Now about once a month i just restore that backup, update my paid apps, extract the apks and install them on my real Rom. Thank you so much for your work!!!
[Magisk] edisonzhong0623:
Hi, thanks for your work.

But I failed to install the NanoMod-patcher-7.2.zip

it said

Updater process ended with ERROR: 1

！！fail to grow magisk.img
[Magisk] edisonzhong0623:
Here's the log:)
[Magisk] Oswald Boelcke:
What's you ROM?

Which Magisk version?

Failure of the patcher occasionally occured to me, too, if I flashed the patcher immediately after Magisk and NanoMod-microG. A reboot into system, back into TWRP, and flashing of the patcher always worked for me.
[Magisk] edisonzhong0623:
thanks man,

I just tried reflashing the magisk and boot, then turn off the hide magisk

then I succeeded in flashing the patch :)

fantastic

---------- Post added at 01:38 PM ---------- Previous post was at 01:10 PM ----------

After setting up my google account, contact and calendar cannot sync, any way to solve that? thanks
[Magisk] Setialpha:
You need to install GoogleSyncAdapter, see http://www.apkmirror.com/apk/google-inc/google-contacts-sync/google-contacts-sync-7-1-2-release/

Or export via vcf, webdav/caldav.
[Magisk] American_Jesus:
Just an update

Looks like i (may) have found the issue with battery drain. I'll just share it in case some one have the same issue.

Notice that some apps where not registered on GCM, and that was the cause of issue, apps keep trying to register and keep draining the battery.

This start to happen after i update my ROM and (somehow) lost my microG settings, and apps were no longer register on GCM, decided to read the microG docs another time and notice this:

So decided to reinstall the apps that use GCM (backup apk+data > uninstall app > restore), with all apps registered on GCM no longer have battery drain.

Now i've 0% battery waisted over night instead of 50%
[Magisk] edisonzhong0623:
Quite weird that I now installed both calendar and contact sync adapter, but I only get contact sync.:confused:
[Magisk] Setialpha:
I'll add a note to the docs.

Dunno, maybe the microg documentation gets you covered, as I never used any goigle sync.