yashsingh1/xdaforums huggingface dataset:
[Magisk] marcdw:
Anyone try NanoMod in a MultiROM environment? crDroid (a secondary on LG G3 D851) has been my microG ROM for a long time but I thought I'd give NanoMod a go.

After a few hours I've failed. ROM will not boot. Initially I'd get the boot animation for some time then the screen goes blank (dark but illuminated). After a few attempts I went with the smaller microG-only zip. Stuck at the LG logo.

Also tried versions 7.0 and 6.x of NanoMod but get stuck at LG logo each time.

ROM with Magisk boots fine as always.

On next attempt I'll see if recovery and MultiROM logs show anything.

Hmm, just saw post from piet8stevens. My other phone is also ZTE Axon 7 with Bliss. I reckon I'll have a go on that also and see if I can reproduce his issue.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Magisk] marcdw:
[MENTION=1835735]piet8stevens[/MENTION], I just had a go with NanoMod on the ZTE Axon 7 (2017U) and Bliss. Patching of the ROM using the zip in TWRP worked without errors. I had about 45GB free before I started.

I noticed you used the script(s) to patch. Is there a reason you didn't use the provided zip instead of generating your own? Just curious.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Magisk] piet8stevens:
Well, that is very interesting. Frankly, I did not use the .zip because on my first read through the instructions, I could not figure out what to do. Then, after running into the problem, I did figure it out (simple really, but you have to read carefully - the underlined parts of text not being links kind of threw me off, believe it or not) , generated the zip with mod.sh and tried that in TWRP. But then, I also run into a problem (probably the same one) but with a different error message as I wrote in my last post before this one.

Now, based on your input, I will reset my phone, reinstall Bliss and run the zip right away to see if that works. One difference: I have a A2017G. I installed the N-modem for G and the universal bootloader - so that should not generate this problem, but you never know.

I used Magisk 12.0 and the 20170501 Nanomod release, full variant. Which ones did you use?

EDIT: l had never noticed the patcher zip on the download page. Instead of generating my own zip, I am now downloading the one provided to test if that gives a different result. [MENTION=6046143]marcdw[/MENTION] Thanks for your comments.

EDIT 1: Result with downloaded .zip is the same as with the .zip I had generated (executed without wiping & reinstalling the ROM).

EDIT 2: I have now reinstalled Bliss, Magic, used the patcher .zip and if fails again with error 1. I have tried using the patcher .zip before and after installing NanoMod itself, but same result.

EDIT 3: OK, found a sequence that works:

a. Flashed the ROM.

b. Flashed Magisk.

c. Booted into the ROM and back to TWRP.

d. Used patcher .zip. It now finished without an error.

e. Flashed NanoMod.

So, pretty much what is written in the first post. What is different from what I did before: I used the patcher after flashing NanoMod (maybe in the first post instructions, using patcher whether from PC or from .zip should be a separate step before flashing Nanomod instead of as a subbullet after flashing Nanomod?). Also, booting into ROM is something I had skipped.
[Magisk] droika:
Thanks [MENTION=4187311]Setialpha[/MENTION] for giving us so much useful feedback (for free)! Just wondering if there's any explanation why the "self check" fails with this LineageOS 14.1 ROM:
[Magisk] kurtn:
I think, that's no nanomod issue. In nougat the location provider has to be a system app.
[Magisk] Oswald Boelcke:
No issue with a failing self check on LeOS 14.1 based Resurrection Remix-N-v5.8.3
[Magisk] Anarchy16:
first of all . im sorry for this . ive been searching for tips/guide/tutorial to install microg but i only got confuse (because im new to this microg things)

can someone give me simple/noob-friendly guide on how to install microg ?

which one should i download ? (look at attachment)

thanks in advance :)
[Magisk] SketchyStunts:
If only wanting microg & not the full nanomod package....

Clean flash ROM

Flash magisk (if its not baked into your ROM)

Flash microg

Reboot

If your ROM doesn't support signature spoofing....

Boot back into recovery

Flash patcher (takes around 10min on my v20 to complete)

Reboot

Go to Microg settings in your app drawer & click on "self check" & enable all check boxes (the bottom 3 won't check)..then

Enable Google device recognition

Enable Google cloud messaging

Then go to unified nip settings....

Click each option & check the checkboxes

Reboot

Open play store & sign in

Profit
[Magisk] Anarchy16:
okay . now i understand . thank u so much sir :cowboy: respect

last thing, what dirrefent between only microg & full nanomod package ?

edit: nvm, i read the op . but still the step of installation are the same, right ?
[Magisk] SketchyStunts:
If doing the full package its

ROM

Magisk

Nanomod
[Magisk] Oswald Boelcke:
Maybe this supports, too.
[Magisk] Setialpha:
What Device? Logcat?

All NanoMod apps are system apps, including microG, so that's not it.
[Magisk] Setialpha:
You need to reboot, that's mandatory because else there's no dalvik cache. Nope, you normally first install NanoMod, the Magisk, but believe, I know what's going wrong, stay tuned.
[Magisk] Anarchy16:
i cant check this 4 option . is that normal ? or i did something wrong ?

edit: device: op3. rom: phoenix aex
[Magisk] Setialpha:
1 - 3: your ROM does not have proper signature spoofing. See first post on how to achieve that (tl;dr flash patcher zip), though this looks strange, please provide a logcat.

4: only active when GPS is active and not in power-save mode
[Magisk] Setialpha:
In the github repository you'll now find the following, which should fix a few more issues with the framework patchers (both on-pc and on-device):

* Internal Changes
* full package: replace `spaces` with `underscores` in Zelda ringtone names
* full package: minor fix in installer
* framework-patcher package: grow and shrink `magisk.img` if required
* fixes issue where patched `services.jar` could not be installed, because not enough space was left in `magisk.img`
* framework-patcher package: show error message to user if `/system` fails to re-mount read-write
* framework-patcher package: unmount `/system` and `/data` after work is done
* framework-patcher script: grow and shrink `magisk.img` if required
* fixes issue where patched `services.jar` could not be installed, because not enough space was left in `magisk.img`
* framework-patcher script: fix installation path for patched `services.jar` when NanoMod is not installed

Please test and provide feedback.

Edit: on a side-note ... anyone tested with a ROM older as MarshMallow?
[Magisk] Anarchy16:
my bad for that bcause i forgot to enable signature spoofing . silly me :silly:

all are checked now but then there this one . what to do now ?

edit: nvm, a restart check that for me :D

btw thanks all for the help . really appreciate that :svetius:
[Magisk] marcdw:
[MENTION=1835735]piet8stevens[/MENTION], you're final steps were similar to mine.

ROM

Magisk

Reboot into system and confirm root (cue from [MENTION=7408621]noc.jfcbs[/MENTION] )

NanoMod

Patcher

OP says patcher after NanoMod.

Did same for another ROM on the G3. Now if only I can get it to boot (a MultiROM thing).

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Magisk] piet8stevens:
Thank you. I have tested as follows:

a. Generated Nanomod zip and Patcher zip from Github.

b. Test without rebooting:

b1. Factory reset.

b2. Flash BlissROM, Magisk, Nanomod, Patcher. Result: same error as before.

c. Test with booting:

c1. Factory reset.

c2. Flash BlissROM, rebooted, Flashed Magisk, Nanomod, Patcher. Result: same functioning OS as before with NanoMod apps, MicroG etc... working (as far as I can tell after having used the ROM for all of 5 minutes).

So, thank you for your effort, but on the basis of this test, I can so no difference between yesterday's version and today's. Should I test differently?
[Magisk] Setialpha:
Rebooting is always required.

The fixes are mainly for users who could't get it to work at all or where it complained about no space left when installing the modified services.jar. In fact, if it works for you like befofe, it means I haven't introduced new bugs. ?
[Magisk] Angelos N.:
Yeah I think it requires official play store and not yalp store. Gonna test later and report back for others.

Edit: It does not even work with play store version. I think something is wrong with it. I will try a different package of microg and I will report if this is a microg problem or nanomod problem.
[Magisk] Mynacol:
Please update MicroG to the latest preview, 0.2.4-108, and tell us how you work out the problems:good:
[Magisk] Setialpha:
I've already instructed him to do, so I assumed he did, becazse that in fact is a requirement.
[Magisk] Angelos N.:
Yes I did so, it comes installed with beta3 of nanomod. I am home now, I am gonna test system mode installation to see if I have different results and I will report back.

Edit: System installation does not work either, going to test a different microg package (not nanomod) to see if this is an issue with nanomod or there is a problem in my end, will report back soon.

Edit2: Seems like there is a nanomod issue, after installing MicroG from MOVZZ ( https://androidfilehost.com/?fid=745849072291696784 ) i get Uber working, but I cannot find myself in the map yet, will report back when I manage to fix that as well.

Also there is a problem when installing both Dejavu and MLS in nanomod, only one is installed.
[Magisk] guest4711:
Tried again on another device with magisk 15.2 running Android N. Still bootloop.

Looking at the installed module I noticed a problem: The swipe libs are copied directly into system, not into system/lib as they should. Afaik magisk does not like files in system...

Edit: Moved the files into lib/ and the bootloop is history.

But nlp did not work as expected. Noticed that the library for GMSCORE was not installed (missing folders lib and lib/arm in priv-app/GmsCore/ and the lib.) After moving the lib in place and rebooting the device nlp was registered and working.
[Magisk] Setialpha:
what's the recovery.log after installing in TWRP?
[Magisk] mathhocraft:
error rh-01

I do not know what happened I'm having this error and I do not know how to solve it I've already been in microg config

I'm using cyanogemmod 13 I do not know if this is the problem

I installed the rom first after that I installed the magisk and after that I installed the nanomod microg in the stable version

I'm having this error rh-01 please help me

(I noticed that I can only log in with google by disabling the

google device registration

google cloud messaging

google safetynet

if they are not able to login

i use lg optimus l3 e425
[Magisk] guest4711:
Here you are.
[Magisk] Setialpha:
Do you have signature spoofing? If ROM built-in you need to enable it for both microG GmsCore and Play Store.

Thanks, a fixed build should roll out today evening.
[Magisk] mathhocraft:
no signature spoofing

do you know another method to enable signature spoofing

I tested with tingle more of the error because it says that rom has .odex

I do not know what I do to have the microg working on cyanogemmod.
[Magisk] Setialpha:
If the ROM is odexed no patcher (needle, tingle, haystack or my NanoMod-Patcher) will work, you'll either have to manually deodex (XDA has several tutorials on that) or use another ROM that already is deodexed. Or, if you don't need to pass SafetyNet use the FakeGApps Xposed module.
[Magisk] tom.android:
If necessary such as official rom (odex rom), I manual patch using baksmali.jar + smali.jar + SmaliPatcher v1.0 (old version). cause i uses magisk module.
[Magisk] ydd0ras:
Can you describe in few works how it works? Thx!
[Magisk] tom.android:
First i appologise to admin for refer another mod.

My Step is

Requirements

- Smali 2.2 or later

- Baksmali 2.2 or later

- Java installed

Steps

- create working directory.

- copy (1 directory 4 files) into this folder.

+ "framework"

+ smali.jar, baksmali.jar --copy from your download.

+ services.jar,services.odex --copy from your framework/oat/arm64.

- run cmd here

>java -jar baksmali.jar x services.odex -d framework\arm64 -o tmp

*** "framework\arm64" assuming your device is arm64 ***

*** otherwise try "framework\arm", if that also fails try just "framework" ***

output

-new directory name "tmp" created.

>java -jar smali.jar a tmp -o classes.dex

output

-file "classes.dex" created.

-open the odexed "services.jar" (from your framework dir) with a zip archiver program (7zip, WinZip etc.)

and add "classes.dex" to the JAR.

and (delete META-INF folder inside jar file), close add file to zip.

-open smali-patcher-program.exe (old v1.0) patch new service.jar in a normal way but use all patch options.

-open final smali magisk module, use only "services.jar" copy it to replace "/system /framework/servies.jar (original)". (I create new magisk module for this step not copy this new services.jar directly to substitute.)

My Nanomod-microG on Xiaomi Official Global beta v8.1.11

Download Tools https://mega.nz/#F!BjwW1KAC!GNWoxyMaMWpPISswbCpiIg

[YOUTUBE]ESlQb6UIi00[/YOUTUBE]
[Magisk] raptorddd:
tingle using computer

need 2 things

framework.jar and build.prop in same folder location

then make flashable or push into system and replace also change permisson.

---------- Post added at 09:48 PM ---------- Previous post was at 09:45 PM ----------

am using lastest stable since yesterday . were using previous build. now am not sure but i dont remeber seeing microg beign the 3rd item in battery stats.. actually ive never seen it there now its the 3rd thing on battery usage list
[Magisk] guest4711:
Thank you, now it worked again for me...Seems everything at the right places again (microG pkg).
[Magisk] ydd0ras:
Wow, many thanks mate for your nice tut. You know I have lot of Mi devices running custom ROMs and the most are deodexed. I have also a Mi A1 with the odexed stock ROM. Have tried many tools for unpacking, deodexing and repacking but I fear my knowledge us to less for this stuff. My deodexed ROMs won't boot properly. I am using microG on all devices as well (for nearly 1 year).

OK, will try to realise that today with your awesome tut.

Here a sample from my microG experience with MIUI 9 (have written more than 12 hours on this):

http://en.miui.com/forum.php?mod=viewthread&tid=725513&extra=

http://en.miui.com/forum.php?mod=viewthread&tid=884539&extra=

Thx
[Magisk] CHEF-KOCH:
Sadly error 1 isn't fixed

NanoMod 14.93 beta (fresh installation so I can't provide any /data/adb/..)

LineageOS 15

Magisk 5.5.5-180113

Patcher or the gaps package both abborting with Error 1

Sadly since the new changes I can't get it to work anymore. :(
[Magisk] Setialpha:
I don't get the error message:

>> chown: unknown user/group root:root

HOW can root be unknown? Also that's nothing new, permissions are set since version 1.0. I'll see if I can find something out, though looks VERY strange to me...
[Magisk] tom.android:
Great Tutorial !!! its my inspiration.
[Magisk] ydd0ras:
Wow, thanks for kind words. But on the other hand I think I am dumb to follow the steps from your tut.

Can I pm you?

Thx
[Magisk] guest4711:
Perhaps it would be safer to use

chown 0:0 filename

This will work even if root is renamed, e.g. admin or toor....
[Magisk] Setialpha:
Likely.
[Magisk] mathhocraft:
i need a help

i give this error ht tps : // pasteboard.co / H2Kfuet .png

remove spaces plz
[Magisk] Setialpha:
So, have you granted the permission? Settings > Apps > App Permissions. See the NanoMod documentation for more detailed instructions.
[Magisk] mathhocraft:
a question

It is necessary to install nanomod microg together with pacher

because I just installed the microg

---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------

after try command nanomod-overlay --permission

i give this error https :/ / pasteboard .co/ H2KwJWu.png
[Magisk] Setialpha:
I don't know whether your ROM is patched or has built in support. If it has builtin support go to Settings > Apps > App Permissions.

If it's not patched, use the patcher.
[Magisk] raptorddd:
Play Store 8.4.*.V introduces internal apk changes, which are not (yet) supported by APK Tool, so I can't provide a newer version right now. To stop the Play Store from constantly trying to update itself (and drain both battery and mobile data), use an application like DisableService, Servicely or-the-like to disable Play Store's 'DailyHygieneService' *AFTER* you've initially setup the Play Store, else it won't sync your installed applications and won't provide you with updates, until you let that service atleast run once. [MENTION=4187311]Setialpha[/MENTION]

i have a question am using stock roms playstore.. is that an issue? or should i use the one provided in zip.

thank you for your hard work and time spent on this .. very appreciated. :good:
[Magisk] Setialpha:
Depends. If it's not updated (and thus a system app), NanoMod's Play Store will be used. If ROM Play Store was updated once (and thus a user app), it will be used instead of NanoMod's Play Store and you'll loose the ability for (in-)app purchases with microG.
[Magisk] BootloopedMillennials:
Adding another case of Error 1 install aborting others are having starting with Nanomod patcher v. 14.93+. It's not a big deal the 14.9 version from mid December worked before and still does, so I used that. Magisk 15.3 (1531) and LineageOS 14.1.
[Magisk] Setialpha:
log?
[Magisk] CHEF-KOCH:
So, only the patcher has the error 1 now. Rest works. :good:
[Magisk] Setialpha:
It says the ROM is odexed.
[Magisk] bonbonboi:
With the latest update now I got an issue in updating/uninstalling the older version of nanomod, last year I installed nanomod as system, then later I installed magisk, now I'm trying to figure out how to uninstall the old version because the new version get installed without overwriting the old version, first what I did I flashed the new version, it didn't detected the old one, fine I uninstalled it, then uninstalled magisk and tried again, same issue the new version doesn't care to deal with the old version, I'm afraid to en up with two nanomod installed. Now I'm looking for those old versions of nonomod which I can find a proper uninstaller to deal with the old version.
[Magisk] Setialpha:
The installation path is the same as before, so I suppose it's the old system mode installation that conflicts... in the first post you'll find links to archived downloads, you'll find snything there, back to version 4 or 5.
[Magisk] bonbonboi:
Ok I did the steps backwards uninstalled magisk to back to the first state when installed nanomod. Then i used nanmod uninstaller of 13/12/2017 to uninstall the system version of nanomod, got an error regrading to com.qualcomm.location but I fixed it with a dummy apk since it seems i deleted its backup, installed the new nanomod version as system again, short of story that mozilla location service is gone and the new location deja vu location service keeps crashing once i activate it.
[Magisk] Setialpha:
Then choose to install Mozilla location backend instead (or both) and provide a logcat, so that the error can be reported to the developer of the Deja Vu backend.
[Magisk] bonbonboi:
java.lang.RuntimeException: Unable to instantiate service org.fitchfamily.android.dejavu.BackendService: java.lang.ClassNotFoundException: Didn't find class "org.fitchfamily.android.dejavu.BackendService" on path: DexPathList[[zip file "/system/app/nlpBackendDejavu/nlpBackendDejavu.apk"],nativeLibraryDirectories=[/system/app/nlpBackendDejavu/lib/arm64, /system/lib64, /vendor/lib64, /system/lib64, /vendor/lib64]]
at android.app.ActivityThread.handleCreateService(ActivityThread.java:3216)
at android.app.ActivityThread.-wrap5(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1597)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:153)
at android.app.ActivityThread.main(ActivityThread.java:6244)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:107)
Caused by: java.lang.ClassNotFoundException: Didn't find class "org.fitchfamily.android.dejavu.BackendService" on path: DexPathList[[zip file "/system/app/nlpBackendDejavu/nlpBackendDejavu.apk"],nativeLibraryDirectories=[/system/app/nlpBackendDejavu/lib/arm64, /system/lib64, /vendor/lib64, /system/lib64, /vendor/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:3213)
... 9 more
Suppressed: java.io.IOException: Failed to open dex files from /system/app/nlpBackendDejavu/nlpBackendDejavu.apk because: Failed to extract 'classes.dex' from '/system/app/nlpBackendDejavu/nlpBackendDejavu.apk': Inconsistent information
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:367)
at dalvik.system.DexFile.<init>(DexFile.java:112)
at dalvik.system.DexFile.<init>(DexFile.java:77)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:359)
at dalvik.system.DexPathList.makeElements(DexPathList.java:323)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:263)
at dalvik.system.DexPathList.<init>(DexPathList.java:126)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:48)
at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:64)
at com.android.internal.os.PathClassLoaderFactory.createClassLoader(PathClassLoaderFactory.java:43)
at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:58)
at android.app.LoadedApk.createOrUpdateClassLoaderLocked(LoadedApk.java:520)
at android.app.LoadedApk.getClassLoader(LoadedApk.java:553)
at de.robv.android.xposed.XposedInit$2.beforeHookedMethod(XposedInit.java:131)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:340)
at android.app.ActivityThread.handleBindApplication(<Xposed>)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1575)
... 7 more
[Magisk] guest4711:
It seems your dalvik cache is outdated. I'd try to wipe cache and dalvik-cache in TWRP and try again. (First boot could need a few minutes longer...)
[Magisk] bonbonboi:
I thought the same so I wiped dalvik & cache, didn't help, any way i back to Mozilla location service.
[Magisk] raptorddd:
am having problems with messenger it does not receive messages if i close app. weird is whats app does. i can receive if am in chat once i leave chat it doesnt.

i usually do clean installation by removing old build and also removing fb/messenger and whats app apps . wipe dalvik and cache install new build create new account check all settings are ticked on microg settings enable device on and gcm registration on too.

proceed to log into account once am in playstore i download fb, messenger and whats app so it registers on microg gcm tab.

didnt have this problem on build. NanoMod-microG-14.8.20171130

UPDATE

found what was causing not receiving messenger notifications.

i have data saver and the apps ive reinstalled werent selected

only on 15 and previous.