yashsingh1/xdaforums huggingface dataset:
[Magisk] pavanmaverick:
Thanks. That worked. However, you are right - it errored out. Going to try just dealing with the .odex files to see if I can get it to work...

---------- Post added at 03:15 PM ---------- Previous post was at 02:30 PM ----------

Oh, man. Now I'm having another weird issue. I started on a clean install of Lineage OS 16 on Pixel (no Magisk!). This ROM has both the .odex and .vdex files. vdexExtract didn't work on the vdex file (since it's Pie, this seems normal?). However, deodexing the .odex file worked without errors/issues. I then ran the patcher (beta v4), and that seemed to work without errors. And then I ran NanoDroid (in System mode - since I didn't have Magisk installed). Seemed to work, without errors. However, after all this, when I reboot, the phone hangs on the Lineage animation, and after a while, it just reboots into recovery.

Trying to reboot from Recovery back into Lineage yields the same result.

Any suggestions? Has anyone else seen this happen?
[Magisk] DoR3M3:
Make sure you use nanodroid_overlay=1 in your .nanodroid-setup...

[MENTION=5882096]AndroidBeginNinja[/MENTION] - Settings > Apps > Permission > Signature Spoofing > Tap 3 Dot menu, show system apps, then give spoofing permission to fakestore, hopefully you installed the fakestore, and give permissions also to microG Services Core.

[MENTION=4187311]Setialpha[/MENTION] ok so I followed the VDEX steps

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

Except since we are running adb, not sure why we mount system in TWRP.

These are the cmds I ran;

adb shell

su

mount -o rw,remount /system

adb pull /system/framework framework

cp framework/services.jar services.jar-backup

vdexExtractor -i framework/oat/arm64/services.vdex --ignore-crc-error

mv framework/oat/arm64/services.apk_classes.dex classes.dex

zip framework/services.jar classes.dex

zip -j framework/services.jar classes.dex

adb push wouldn't work for me, so I just copied services.jar to my phone, and then copied it over to /system/framework

Then I ran;

adb shell

su

chmod 0644 /system/framework/services.jar

chown root:root /system/framework/services.jar

Stock Oreo this all that's in services.jar;

META-INF/MANIFEST.MF

So I as I mentioned I ran the cmd without -d as;

>zip framework/services.jar classes.dex

adding: classes.dex (deflated 55%)

Now when I unzip it I have

~/Downloads/services >ls

META-INF classes.dex

NanoDroid-Patcher failes in TWRP for me;

odexed ROMS are not supported

Updater process ended with ERROR: 1

Error installing zip file...

I've attached the recovery.log if it helps...

Thanks

P.S. After posting all this I see there is now the NanoDroid-patcher-18.0_beta1+vdex_4.zip to do this automatically... Sheesh I can't keep up with all the changes going on, you're a busy person Setialpha LOL... Do we need to make the system R/W in TWRP before using this>?
[Magisk] starbright_:
Added my log from a Oreo phone (vdex_4).
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION], I installed back a clean BACKUP of Stock Oreo 8.1.0 in TWRP, only rooted with Magisk, no modules, no microG, no Xposed.

I booted into TWRP and clicked on System to mount it, then installed NanoDroid-patcher-18.0_beta1+vdex_4.

Not sure if it's normal, but after about 1 minute, the screen went blank and flashed on and off several times, then at about 3-5 minutes later, just sitting blank, so not sure if it's still working? I assumed it would just sit in the TWRP screen working...

hmm
[Magisk] starbright_:
It can run 5 ... 15 minutes, for me it is over after few seconds (due to an error).
[Magisk] DoR3M3:
Flashing NanoDroid-patcher-18.0_beta1+vdex_4 I've been sitting 30 minutes with a blank screen, not looking good...
[Magisk] Setialpha:
This issue can be fixed. New build later today.
[Magisk] Setialpha:
OK, it's getting further than before, but baksmali doesn't like to run on SDK lower than 26 (Oreo), I guess I'll have to use two versions of baksmali, on for Oreo and newer and a second for Nougat and older, let's see.
[Magisk] Setialpha:
You may try 'adb pull /tmp/recovery.log' to grab the log and then forcefully rebooting by pressing the power button for a given time.
[Magisk] HyperCriSiS:
Can you put that in OP?

https://www.bountysource.com/issues/51518216-gcm-fcm-update-needed-for-push-messaging
[Magisk] Setialpha:
I will, when I'm at home.
[Magisk] DoR3M3:
Ok will try...

[MENTION=4187311]Setialpha[/MENTION] recovery.log attached... ;)

Thanks
[Magisk] the.D:
[MENTION=4187311]Setialpha[/MENTION] I've noticed that location services are not working for some apps (ex. Pokemon Go) on Oreo and Pie but do on Nougat. :confused:
[Magisk] Setialpha:
Can't reproduce, works fine, here on Oreo, haven't tested on Pie yet, though. Maybe the logcat contains useful info?
[Magisk] Souvikhazra80:
Using nanomod patch from N,waiting patch for P.:)
[Magisk] Setialpha:
Patcher 18.0~beta1+vdex_5

Hi all, a new beta build for the Patcher is now available.

Changes:

now features two baksmali / smali builds one for SDK lower than 26 (Marshmallow, Nougat), and one for SDK 26 and up (Oreo, Pie)

Patcher now exists on Pie (as it's not yet fully supported)

Patcher now mounts /vendor partitions, which increases ROM compatibility

Feel free to test on any ROM older than Pie.

On a side note: I'ved added a big fat banner on the first post, as there's currently going a bounty regarding crowdfounding a developer how implements FCM in microG.

You may wonder, so... can I actually have signature spoofing on Pie yet? Hmm... yes. IF your ROM's services.jar already contains a classes.dex, you should be able to use the latest baksmali/smali from git to unpack and re-pack that classes.dex on your PC and then use the Patcher 18.0~beta1 (NOTE: 18.0~beta1 NOT! 18.0~beta1+vdex) to apply the patch. See the docs for more infos. Success NOT garantueed and for now

no

support for Pie, until all tool are updated!
[Magisk] tom.android:
error_log test_5
[Magisk] HemanthJabalpuri:
Sir sdk 19 error 1 in twrp
[Magisk] Setialpha:
It just segfaults without any further message. I suppose it's just too old of a ROM. But: it's already deodexed, so can use [MENTION=5627087]ale5000[/MENTION] Tingle instead.
[Magisk] HemanthJabalpuri:
Sir I dont have pc...so i am using your patcher sir...

Please give another way to patch without pc..sir
[Magisk] Setialpha:
Patcher 18.0~beta1+vdex_6

Another beta for the Patcher.

This time I've successfully tested it on my Nexus 6 with Resurrection Remix Nougat and LineageOS 15.1 aswell.

Feel free to test. NanoDroid-Patcher-18.0~beta1+vdex_6.zip
[Magisk] tom.android:
can't downloaded NanoDroid-patcher-18.0~beta1+vdex_6.zip
[Magisk] Setialpha:
uff... XDA seems to be having issues currently. edited post with if a link.
[Magisk] tom.android:
error_log_test6
[Magisk] starbright_:
I am sorry, no luck.
[Magisk] Setialpha:
It complains about missing a Java class, though my baksmali/smali builds used are the "fat" ones, which should include enough to run on a complete Java setup. I can't reproduce this on any tested ROM (RR, LOS, NOS, PE), out of curiosity: what ROM is that?
[Magisk] tom.android:
Official MIUI-10 China ROM Lastest 8.27.2018 For Mi Max2

Fresh installation (Nothing in stalled)
[Magisk] Setialpha:
Strange. Coud you please issue the following commands from adb shell while in TWRP?

mount /system
mount /vendor
find /system -type f -name '*libcamera*' > /sdcard/FIND_LOG
find /vendor -type f -name '*libcamera*' >> /sdcard/FIND_LOG

and post the file FIND_LOG from your internal storage here.
[Magisk] Setialpha:
When you manually deodex services.jar (I guess you do, as you posted patched services.jars recently), what's your baksmali command?
[Magisk] tom.android:
I'use FulmicsDeodexer v.16

and sometime

java -jar baksmali.jar x services.odex -d framework\arm64 -o tmp
[Magisk] starbright_:
Sorry, took a while.
[Magisk] Setialpha:
Patcher 18.0~beta1+vdex_7

The last Patcher beta build for today.

recovery.log will now store all mounted volumes

expand LD_LIBRARY_PATH

improve support for ODEX format

other minor changes

Feel free to test.

NanoDroid-patcher-18.0~beta1+vdex_7.zip
[Magisk] tom.android:
error_log_test 7
[Magisk] Setialpha:
I can't change the fact that it's missing some Java class, sadly, so you're stuck with manual deodexing for now.
[Magisk] starbright_:
Seems error keeps the same, we need another trial ;)

I don't understand:

>> patching services.jar

Error preloading public library libandroid.so: dlopen failed: library "/vendor/lib/libcamera_client_shim.so" not found

libc: Fatal signal 6 (SIGABRT), code -6 in tid 2449 (main), pid 2449 (main)

This file is available!?!?

a3xeltexc:/vendor/lib $ ls -l libcamera_client_shim.so

-rw-r--r-- 1 root root 6040 2009-01-01 01:00 libcamera_client_shim.so
[Magisk] tom.android:
Thank you for your working hard.
[Magisk] Setialpha:
That... doesn't make sense. What happens, when you run

'mount /vendor'

before flashing the Patcher?
[Magisk] starbright_:
I get : can't find /vendor in /etc/fstab.

In fact in filemanager I can't see this /vendor (TWRP)

It is in /system/vendor/lib.

The find.log - I created that after booting into Android. Maybe it is different mounted there....

I see, that in Android /vendor is linked to /system/vendor

It seems this link is not already there in TWRP.

I created in terminal/TWRP the link, now it does something .... Let's see the results....
[Magisk] Setialpha:
That makes sense. I'll see, if I can cook something up.
[Magisk] starbright_:
Hurrayyyy, it worked. Spoofchecker is green. The link solved the issue. Thanks, man!

I should have seen that earlier.... :(

Now I can set it up from scratch ....
[Magisk] saturday_night:
My Google Account doesnt exist on my phone and Apps still working. But after i first installed microG nanomod, i used the play store (sure with my google account), installed my Apps, dissabled play store, rebooted and installed fake store. Everything is working. For updating my Paid Apps i have a small backup of slimrom with play services and store + apk extractor. By time i restore that backup, update my paid apps, extract the apks and install the updates to my real used Rom.
[Magisk] Setialpha:
Of course that works, as apps verified their license while PlayStore was active. FakeStore can't do that, but the license is still valid, so the apps don't request a check again.
[Magisk] lucastracq:
hi there. i'm using nanomod (f-droid and microg) on a build of omnirom and i have two minor problems.

first of all boot time increased a lot but just at the bootlogo, instead it takes the usual time at the bootanimation. it's not a big deal, but i want to be sure that it's something related to the modules or magisk or similar.

the second thing is that after every boot i get a notification of google play updating, why does it happen?

thanks in advance to anyone who will answer.
[Magisk] Setialpha:
Longer boot time is normal.

PlayStore tries to update itself, but fails, that's it. It's intented behaviour. As mentioned in the README, I modified it to allow in-app-purchases, which normally don't work with microG.

The last time I checked, apktool did not support InstantApps, thus I couln't modify the latest PlayStore release yet. I'll check again if apktool is IA ready soon.
[Magisk] lucastracq:
ok, sorry, i actually read about this but i get no error or force close so i thought it was a different problem, also because it did update to the new interface. anyway now it makes more sense and please take your time, this thing it's already perfect! :)

thanks a lot!
[Magisk] Setialpha:
9.0 Beta1

So Version 9.0 Beta1 is now available for testing. This release brings in a few app updates:

* Simple Calendar (2.4.3)
* Simple Gallery (2.10.4)
* NewPipe (0.9.7)
* Nominatim Nlp Backend (1.2.2)
* Termux (0.50)
* PlayStore (7.7.57.O)

but most importantly: it features a shiny new installer

cleaner, easier to maintain code

Maps API version 1 now installed by default

several improvements regarding system mode installation

The flashable beta zip can be downloaded from AFH.

For anyone interested the new installer can be viewed here.

The new installer is currently only used for the full package. The installers for the F-Droid and microG packages, awell as the patcher zip will be updated soon.
[Magisk] Setialpha:
9.0 beta2

9.0 beta2 is now up, changes since 9.0 beta1

minor fixes in installer for full package

new installer for F-Droid package

new installer for microG package

fixes regarding GNU Bash in microG package

please test and report any occurring issues.

Download from AFH.
[Magisk] bhanuprasad1981:
Tried both beta 1 & 2 I am struck at just a sec screen while adding Google account
[Magisk] Setialpha:
Is your framework patched and microG properly setup?

If so, I need a logcat. Someone else reported that issue already on microG github, it's a rare microG issue.
[Magisk] bhanuprasad1981:
I am using aosp extended ROM on One plus 3 it has inbuilt support for signature spoofing I already enabled it ,everything seems OK in microg self test how can I provide log cat
[Magisk] marcdw:
Now that crDroid is available on the Axon 7 I tested beta 2 of microG and F-Droid zips. Currently without Magisk.

Play Store does not get installed. I keep getting Yalp Store instead. Is that by design? TWRP output shows Play Store.

LG G3 D851, crDroidAndroid v3.2 ROM, microG (NoGapps), MultiROM, Tapatalk 4.9.5
[Magisk] Setialpha:
I'll have a look. Of course that's not intended.
[Magisk] marcdw:
Ah, but I've got more for you. Doing a lot of flashing here.

Flashed ROM with Magisk and then microG. Now I get the Play Store but the launcher is removed (well, not really I discover). Did it a few times. No launcher so I get a home screen with "Android is starting".

Flashed all again along with Pixel Launcher and things are good.

Now if I disable the microG module and reboot I'm presented with the default launcher as well as Pixel. So the launcher gets disabled somehow when using Magisk.

Last test before sleep. ROM, Magisk, F-Droid package. All good. Which means I had to test one more time with microG package. Yep, no launcher.

Sorry I don't have a log for you at the moment. Will have to restore a working ROM first on that device (Axon 7, 64-bit).

LG G3 D851, crDroidAndroid v3.2 ROM, microG (NoGapps), MultiROM, Tapatalk 4.9.5
[Magisk] Setialpha:
You're right. I'll fix it, later today.
[Magisk] Strigae:
Same here. Using version 7.2 for now. :)
[Magisk] Setialpha:
I can't see the issue, the installer is correct and I successfuly tested on my devices.

Did you install FakeStore before? If so, that's the issue as they have the same package id, remove FakeStore first.

Else I need a logcat.

>>>>>

Also I can't reproduce your launcher issue. You're installing in system mode, where the pseudo-debloat feature is neither used nor does it work in system mode. I need a logcat, as I can't reproduce the issue here.
[Magisk] Setialpha:
9.0 beta3

9.0 beta3 now available for testing, changes since beta2:

drop Launchers from list of pseudo-debloated applications in microG package

This prevents Launchers from disappearing when installing the microG package as Magisk Module (the pseudo-debloat feature is not used when installing in system mode). The full package delivers OpenLauncher so it's not an issue there, but the microG package does not ship a launcher on it's own. See Alter the list of pseudo-debloated applications in the README for more information on what that means (and how to adjust to your liking).

Aswell as a few application updates:

* VLC (2.1.8~beta)
* Yalp Store (0.15)
* Twidere (3.6.15)
* OpenLauncher (0.5.1)
* Open Camera (1.38.1)

Download from AFH.
[Magisk] piet8stevens:
Bootloops & 8.0.20170521 without magisk

My ROM (BlissROM on Axon 7) with Magisk full version was working really well. Then, I flashed a camera zip and trouble started: I can no longer boot into Android. After reflashing my rom, rebooting into it, then flashing magisk and nanomod (0521 version), I can enter my encryption pin, but then I go into a bootloop. I tried to avoid this by only flashing nanomod (so without magisk), but then the installed still says it is flashing nanomod as a magisk module. I can boot into android, but no nanomod apps are present (like k9mail, microg etc...).

Any ideas?

EDIT:

I now installed magisk and then used the magisk uninstaller to uninstall. Then, a nanomod install without magisk says it is installing itself into system. I now have microg etc... . But TiBu cannot acquire su privileges. Does the Nanomod version installed into system also provide the phh su?

It is highly unlikely this problem is related to nanomod, but I do not know where else to post.

Thank you for any clues.

EDIT 2:

After above edit, I again flashed the rom, flashed magisk and nanomod and now it works again. The removal of magisk by using the removal zip was the key to getting out of my problem. That cost me a day of trials to figure it out.
[Magisk] marcdw:
No FakeStore or anything. I was starting fresh.

The loss of the launcher stuff happened when using Magisk, as stated, not /system install.

The not getting Play Store was with the /system install.

I had a log ready to post right now but I see beta3 is up. After work I'll give everything a go again.

Well, here's the recovery log from beta2 testing anyway.

https://mega.nz/#!CVwhXIhD!wuLYQ5Cef6mrWs8d8a93qIZTkV5X5fKlfGLFkKQZcVo

ZTE Axon 7 A2017U, AOKP ROM, AX7.Hybrid.R21 Kernel, Tapatalk 4.9.5
[Magisk] anunaym14:
HEY!

Firstly, thanks a lot for keeping the great work on!

I have faced a weird issue on the latest stable!

I flashed f-droid and micro-g variants!

Some of the stock apps of my ROM disappears after flashing these!

Apps include : Gallery, Messaging, Camera etc.

Is it normal?

Never faced it on previous builds!

For confirming I tested this on two different ROMs - AOSP-JDC and Dirty Unicorns!

Also, on JDC, Play Store kept crashing and it updated itself after every crash!

Yet to test that on DU!

Hoping for a help!

Thanks in advance!

Edit: Yes, the same issue happens with DU too!
[Magisk] ska7:
does all this new beta patch can be test in pie?
[Magisk] DoR3M3:
[MENTION=4187311]Setialpha[/MENTION] did you see my recovery log?

https://xdaforums.com/showpost.php?p=77451024&postcount=3755

I forgot to ask, does this new patcher also work for Stock Oreo 8.1.0?

Also I noticed the services.jar is empty, so is that the problem? So I ran the cmd zip without -d to add in the classes.dex that was created from the VDEX DOCS, zip framework/services.jar classes.dex

Stock Oreo services.jar;

META-INF/MANIFEST.MF

Also can you please keep the DOCS updated, so we can also do this manually ourself? I know you're having fun with this patcher, hehe, but I like to hack on it too... :)

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

Thanks for all the hard work, it's great!
[Magisk] gehess:
There's currently a Bounty going on to crowdfund a developer who implements FCM support in microG

FTFY :good:
[Magisk] DoR3M3:
[MENTION=7586138]tom.android[/MENTION]

zip error: Nothing to do! - I'm assuming you also have a empty services.jar and "zip -d" is the problem here...

Hmm
[Magisk] HemanthJabalpuri:
[MENTION=4187311]Setialpha[/MENTION] is SDK 20 i.e., 4.4.4 supported or not?
[Magisk] abacate123:
KitKat is SDK 19, SDK 20 is the 4.4W, which's the wearable version of KitKat back in the day. You can see more explanation about it here. And yes, KitKat is supported, as you can see in the first page, but only in system mode (since magisk only supported 5.0 and above).
[Magisk] Setialpha:
That's not an issue. IF services.jar already contains a classes.dex, -d would remove it.

Not for deodexing. Patching a already deodexed SDK 19 ROM may work, though.

This, except for deodexing with the latest patcher beta.
[Magisk] Setialpha:
So it works. I know install_addond() throws a few errors, but they don't matter yet and will be corrected to install a proper addon.d until the next beta.
[Magisk] Setialpha:
Yes, I currently have a backLOG (pun intended).

You tell me whether it works on Stock Oreo?

I'll update the doc regularly.
[Magisk] Setialpha:
Sänk ju wäri.
[Magisk] DoR3M3:
Yes I see you a working Machine! ;)

No this isn't working if you recall, my screen goes blank and just sits there and won't come back, so you asked me to put up a recovery log, which I did.

https://xdaforums.com/showpost.php?p=77451024&postcount=3755

I thought we want the classes.dex inside the services.jar?

zip -d framework/services.jar classes.dex I thought the idea here is delete any classes.dex in the orignal services.jar and add in the new one we've created?

Thanks again...

P.S. I'll try the latest Beta7 and get back...
[Magisk] HyperCriSiS:
Apps in overlay list were not deleted.

The script does not find the folders.

Strip directory path and .SUFFIX from FILE moving to /sdcard/nanodroid_backups: BasicDreams mv: can't rename '/system/app/BasicDreams': No such file or directory moving to /sdcard/nanodroid_backups: Browser mv: can't rename '/system/app/Browser': No such file or directory moving to /sdcard/nanodroid_backups: CellBroadcastReceiver mv: can't rename '/system/priv-app/CellBroadcastReceiver': No such file or directory moving to /sdcard/nanodroid_backups: DeskClock mv: can't rename '/system/app/DeskClock': No such file or directory moving to /sdcard/nanodroid_backups: DotPapers mv: can't rename '/system/app/DotPapers': No such file or directory

What did I do wrong?
[Magisk] JRapsky:
didn't work for me, treble LOS 15.1 on Moto Z2 play