Android 11 signature spoofing

This script automatically pulls the services.jar from your android device, Patches it with Haystack for android 11, and then compiles it back into a flashable magisk module.

This script is intended to be run on a linux system (WSL should work)

ADB and java are required.

If ADB is not enabled, or fails to find the services.jar file, this script may produce a bootloop causing magisk module, (if you dont know how to resolve this from the recovery, use the manual installation)

Run adb devices to make sure your phone is connected, and that it is the only connected device.

For this script to work you must be in rooted adb mode, run adb root to restart adb in root mode

1) — Working directory

Create a folder to house all the files required.

2) — Download files

Rename spoof_AVDapi30.zip.ONLY’MAGISK&ANDROID-STUDIO to spoof_AVDapi30.zip .

Move dexpatcher-1.8.0-beta1.jar inside the new haystack-11-attempt folder.

Run the following command using rooted ADB to fetch the file we are going to modify.

adb pull /system/framework/services.jar

Then copy it into the haystack-11-attempt folder.

With java installed in a linux environment, run the following command inside the haystack-11-attempt folder.

java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex

This should create several new classes.dex files.

Create a repack folder inside the haystack-11-attempt folder.

Then run zip -j repack/services.jar classes*.dex to create a new services.jar

9) — Swap in new file

Go back to the first folder and unzip the spoof_AVDapi30.zip file (take note of which files belong to it)

Delete the old services.jar located at system/framework/services.jar and replace it with the file from the repack folder.

10) — Re-packing the magisk module

Put all the unzipped files back into a zip file named spoof_AVDapi30.zip And install this as a magisk module.

If your phone is still plugged in you can run adb push spoof_AVDapi30.zip /storage/emulated/0/Download/ to send the file to your phones downloads folder.

The script and this documentation was created by myself.

About

A script that can be used to inject signature spoofing support into unsupported roms such as LineageOS.

Источник

Signature Spoofing on unsuported Android 11 (R) Roms

suleymanov_aydar

Member

How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing?

In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted

I use TWRP recovery but this should not matter !

First of all Flash your ROM and Magisk (you need to download the latest version to get Magisk working on Android 11)

Link for my ROM in case anyone needs it:

Click on Build number (7x) to enable Developer Options

After that enable ADB-Debugging and Root-ADB-Debugging in your ROM in case of LineageOS go to Setting -> System -> Developer Options

So Lets go this is the more complicated part. but also really easy if you done it once.

I’m using Debian Linux but it should be possible on every OS. In Windows use the Linux Subsystem.

You need to have ADB installed on your System tho.

First of all you need to download this 2 Files:

spoof_AVDapi30.zip.ONLY’MAGISK&ANDROID-STUDIO · 11-attempt · oF2pks / Haystack

Rename «spoof\_AVDapi30.zip.ONLY’MAGISK&ANDROID-STUDIO» to «spoof\_AVDapi30.zip»

So now unzip the haystack-11-attempt.zip and put the dexpatcher.jar file into to Folder.

This part I use Bash shell in Linux.

After that you should have a new services.jar in your repack Folder.

Now You need to open the spoof\_AVDapi30.zip go in /system/framework/ and delete the old services.jar and put your own file in. that’s in your repack Folder.

Don’t ruin the zip-format of the file tho because otherwise Magisk will cry while install.

After that put your spoof-AVDapi30.zip and your microG\_AVDx86api30\_magiskMaRViN.zip on your Phone and Flash via Magisk.

Reboot and you hopefully have Signature spoofig working. If you run in any Problems check out the GitHub Links here. there will be comments that maybe will help.

I also want to credit the real developers of this
on xda: Lanchon (DexPatcher & Haystack)
https://forum.xda-developers.com/m/lanchon.4141005/

I’m Sorry if there is ****ty English.
The best of luck for you guys i hope this helps.

JohnWick020

New member

Gionathan

Member

Spidersoft

Member

Thank you very much, I can confirm it worked for me on a clean install of LineageOS on Oneplus 5t.

I have a question concerning updates. When I flash an update via the build in updater (and TWRP) after restarting it takes about 30min to 12 hours for the device to enter a soft boot loop. I think this might be related to not doing the spoofing procedure again after updating. Because everything’s fine again, when I downgrade to previous rom version in TWRP.

So can somebody confirm I have to redo all steps mentioned in OPs post after updating the rom?

abrahamjohn731

Senior Member

For windows user install this : https://www.java.com/en/
After that take your services.jar of your current rom in system/framework/services.jar
and paste with same folder of haystack and dexpatcher
After that hold shift in your folder and right click choose open powershell or cmd here
After that write this command : java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex
you should get 4 .dex file in your current folder and copy that files to your phone

after install mixplorer in your phone and terminal emulator after that go to your directory where you save 4 dex files
and write this in terminal :

Akbar KanColle

Member

abrahamjohn731

Senior Member

My services.jar file can’t be patch with this tool.

Crayvolt

Senior Member

nasim7500

system has signature spoofing support- check

only this two is not enabled
system spoof signature cant toogle- not check
playservice gmscore has correcty signature- not check

Akbar KanColle

Member

My services.jar file can’t be patch with this tool.

abrahamjohn731

Senior Member

kurtn

Senior Member

Zha Revnart

New member

nanodroid have documentation of it

GitHub — Nanolx/NanoDroid: [MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository

kurtn

Senior Member

nanodroid have documentation of it

GitHub — Nanolx/NanoDroid: [MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository

New member

shrubthebub

New member

Kingslayer9988

Member

breversa

Senior Member

@Kingslayer9988 Thanks a lot for your guide, it really helped me out !

You could improve the formatting even more. For instance, there are several occurences of «\_». You could also use the inline-code tags for path/file names.

Khh77776

Member

Similar threads

spoof_AVDapi30.zip.ONLY’MAGISK&ANDROID-STUDIO · 11-attempt · oF2pks / Haystack

Rename «spoof\_AVDapi30.zip.ONLY’MAGISK&ANDROID-STUDIO» to «spoof\_AVDapi30.zip»

So now unzip the haystack-11-attempt.zip and put the dexpatcher.jar file into to Folder.

This part I use Bash shell in Linux.

After that you should have a new services.jar in your repack Folder.

Now You need to open the spoof\_AVDapi30.zip go in /system/framework/ and delete the old services.jar and put your own file in. that’s in your repack Folder.

Don’t ruin the zip-format of the file tho because otherwise Magisk will cry while install.

After that put your spoof-AVDapi30.zip and your microG\_AVDx86api30\_magiskMaRViN.zip on your Phone and Flash via Magisk.

Reboot and you hopefully have Signature spoofig working. If you run in any Problems check out the GitHub Links here. there will be comments that maybe will help.

I also want to credit the real developers of this
on xda: Lanchon (DexPatcher & Haystack)
https://forum.xda-developers.com/m/lanchon.4141005/

I’m Sorry if there is ****ty English.
The best of luck for you guys i hope this helps.

I get a flickering screen here after reboot. And message the Playstore has been closed several times. Maybe I need to delete playstore or first?
Playstore and everything has been still on my device, as I would just spoof it (first). But — during installation with Magisk I get a message that no playstore is available so fakestore will be installed.

I give it a second try just install the spoof_AVDaoi30.zip. Result was exactly same as with installing NanoDroidPatcher via Magisk — Bootloop.
I am wondering why I put the service.jar into the package and the upload the whole thing. Does this make sense? The services.jar is on device, why this should be included into the package?

the services jar starts out on your device. it gets pulled to your pc and the other files you download from the OP make the adjustments to it for signature spoofing. Then it replaces the existing services.jar in the zip you downloaded from the OP so you can use magisk to flash it back into your device, returning to whence it came but now with adjustments.

Don’t worry about the flickering screen and all the messages, that’s normal. Just try to do what you need to working around them, yes it’s annoying and makes it seem like you broke something but you didn’t.

I didn’t use the nanodroiod zip, the other zip the OP provided, I used the microg one from the magisk repo. I know that one works fine. I noticed the nanodroid one tries to place the apks back into the product/priv-app where the originals should go, and even the new system_ext folder for the gsf one. maybe that’s not good on some devices. I couldn’t get it to work and had to abandon it. The magisk microg only uses /system/priv-app and it works fine for me.

read the instructions on the magisk microg, it tells you to put a playstore apk into /data/adb before flashing if you want to use the real store, otherwise the fake store will be installed. ( you can always debloat that one and use the app systemizer module to cram a playstore there later)

Читайте также: Flash plugin для android

re: bootloops, sometimes it works if you just hold the power button and kill it, then let it try again. It worked for me that way today. I had to do that a couple of times when rebooting until finally it’s just back to normal now and boots as quickly as it ever did.

Источник

[INDEX] How to get Signature Spoofing support

lee.wp14

Senior Member

I N T R O D U C T I O N
Signature Spoofing is a feature that allow apps to impersonate themselves as other apps. It works by faking the package signature of an app as the one that the app is trying to spoof.
This feature is common among microG users, as it is required for microG’s custom implementation of Google Play Services to work fine.
If you do not understand what microG is, you should consider leave this page. You are probably trying to do something dangerous. If you know exactly what you are doing, you may however proceed at your own risk
Thanks to @Primokorn for starting this thread and maintaining the list previously!

I M P L E M E N T A T I O N
You have 3 options. Read carefully to determine which option suits you the best.

AospExtended (AEX)
Android Ice Cold Project (AICP)
AIMROM
Android Open Source Illusion Project (AOSIP)
ArrowOS
CarbonROM
Corvus ROM
crDroid
dotOS
Ground Zero ROMs (GZOSP)
Havoc-OS
LineageOS for MicroG
MSM-Xtended
OmniROM

Android Open Source G-OS Project (AOSGP)
Atomic-OS
Cardinal-AOSP
CitrusCAF
HalogenOS
Hexa-Project
MarshRom
nAOSProm
Nitrogen OS
Tugapower
Validus
ViperOS
XOSP

Introduction
microG GmsCore is a FLOSS (Free/Libre Open Source Software) framework to allow applications designed for Google Play Services to run on systems, where Play Services is not available. If you use your phone without GAPPS this might become a useful tool for you.
microG GmsCore is one of the two core components of the microG project.

IF YOU WANT A XPOSED MODULED
You can simply use this Xposed module: FakeGapps (tested on Oreo 8.1 by @kurtn)

IF YOU DO NOT USE XPOSED
You can use Tingle but you have to run it each time you install a new ROM or a dirty flash. The ROM has to be deodexed. Thanks @ale5000
Haystack is also a solution.
Do you know NanoDroid? It’s a microG installer with a large selection of useful apps. Additionally there is a flashable zip to patch your ROM. It automatically re-patches after a dirty flash (e.g. OTA update). No adb/PC required! (thanks @Setialpha)

Your last option is to use a custom ROM that includes the signature spoofing patch. Here is the list:
The signature spoofing option is normally available at the bottom of the dev options or in Settings > Apps > Advanced (gear icon) > Additional permissions. Or simply ask the permission from microG’s self-check screen.

• AEX AospExtended
• AICP
• AimRom
• AOSGP
• Android Open Source Illusion Project (AOSIP)
• AtomicOS
• CarbonROM
• Cardinal-AOSP
• CitrusCAF
• crDroid
• dotOS
• Ground Zero Roms aka GZR: Tipsy
• HalogenOS
• Havoc-OS
• Hexa-Project
• LineageOS (unofficial builds for several devices) thanks to @Simon94 // Official website: https://lineage.microg.org/
• MarshRom
• nAOSProm
• NitrogenOS
• OmniROM
• Tugapower
• Validus (Oreo at least)
• ViperOS
• XOSP

Signature spoofing is also supporting on these specific custom ROMS:
Click here

Thanks to all these developers.

PENDING REQUESTS TO INCLUDE SIGNATURE SPOOFING IN THE FOLLOWING CUSTOM ROMS

Источник

Android 11 signature spoofing