yashsingh1/xdaforums huggingface dataset:
[Magisk] JEANRIVERA:
Failed installation on OnePlus 12 magisk I tried v1.0.1 also same result
[Magisk] k1984228:
i m using Kitsune Mask too, i use shamiko 0.75ver is ok but still can pass strong intergity
[Magisk] ComradeWave:
Failed installation on Xiaomi 11 Lite 5G NE, I digged around a bit and found out that apktool does NOT support DEX files version 040. So it's probably that.
[Magisk] ComradeWave:
I could suggest using the bleeding edge version of apktool, which is here
[Magisk] Vision:
Oh yeah, old version, thanks for reminding.

You write can pass strong.

You mean can't pass strong?
[Magisk] k1984228:
i mean can't pass as well as all intergity
[Magisk] Vision:
So with Kitsune Mask and shamiko (old version) you pass 2/3?
[Magisk] ComradeWave:
I still can't manage to get the module to work lol, even if i decompiled framework.jar manually, it still doesn't find engineGetCertificateChain altough it exists.
[Magisk] badabing2003:
switched from PIF fork script only mode to shamiko, disabled denylist.

Pixel 5

Without shamiko I was passing device.
[Magisk] immortalwon:
Did you apply the latest certificate chitero spoke about in latest frameworkpatch?
[Magisk] Sucharek 233:
Installing this module fails for me

I'm on munch with AOSPA Uvite Beta 4

I'm getting this error:

newApplication method not in Instrumentation.smali

Here's my framework.jar: https://mega.nz/file/RmJG1bZI#SGuATRB7drNCJ5e1RL8o_DCWZbi2pmHrAzlXhwDTAFY

Edit:

After decompiling framework.jar myself, I did find the newApplication method:
[Magisk] ComradeWave:
Here's my framework.jar, it just doesn't unpack the framework.
[Magisk] Vision:
I think this is only if keybox.xml have 3 certificate.
[Magisk] kangwosuck:
Stock room + KSU . Device: pixel 6a . Successful but bootlop issue. Android 13 😵‍💫😵‍💫😵‍💫. Do you use fingerprint screen lock?
[Magisk] RAZINARES:
Yes i use fingerprint screen lock, but how is that related to integrity tho 😂
[Magisk] JazonX:
Fold 5 (One UI 6) - June Patch.

Module Successfully flashes. No Errors, Answered YES to all 3 questions.

Then Removed, Flashed 1.0.1 as well.

Shows No Integrity at all in both versions - 0/3 fails.

- No PIF, Only Shamiko / ZygiskNext / LsPosed

- Stock Rom and Kernel, System with R/W

Additional Info;

Kernel - Not Banned

Signing Keys - Not Test Keys.
[Magisk] kangwosuck:
Did you select all YES questions when installing the framework?
[Magisk] AvisAile:
Wow! With this module install and Shamiko, I pass Strong certification!!!! I hope this will last, I hesitated to unroot my phone... (Pixel 8 - Android 15)

But I don't pass anything if I enable Lsposed :/
[Magisk] Usama-CW:
Thanks for the module, Device Integrity passing without any issues in v1.1.1 UwU
[Magisk] JazonX:
Skipped last two options ?

This patch is optional but recommended if your device has StrongBox or app attestation key support.
Do you want to apply this patch?
- YES [Press volume UP]
- NO [Press volume DOWN]

Skipped patch for ApplicationPackageManager.smali

This patch is for spoofing a locked bootloader for local attestation.
Do you want to apply this patch?
- YES [Press volume UP]
- NO [Press volume DOWN]

Skipped patch for AndroidKeyStoreSpi.smali
[Magisk] badabing2003:
I missed that post, where?

This has not changed for a month

FrameworkPatch/app/src/main/java/com/android/internal/util/framework/Keybox.java at main · chiteroman/FrameworkPatch

Modify framework.jar to build on system level a valid certificate chain - chiteroman/FrameworkPatch

github.com
[Magisk] Hausemaster:
One ui 4.1 just passes basic
[Magisk] Usama-CW:
yes i skipped because

1) My device which is poco x3 pro (vayu) is non strongbox, that's why i skipped.

2) Spoofing a locked bootloader for local attestation didn't worked for me. (momo & native detector)
[Magisk] JazonX:
Answered all 3 questions Yes ?

Any other Modules Installed ?
[Magisk] JazonX:
Thank you for this! Much appreciated for the comment !!!!

So while LSPosed is around, This fails .. Yeah?

Too bad, LsPosed has a few things i need - Knox Patch, Screenshot DRM patch.
[Magisk] Hausemaster:
All 3 questions yes

No other modules installed
[Magisk] thecoolkid:
Is there a tool or a way to sign a build that was signed with test keys to be signed with release keys without rebuilding from source?
[Magisk] immortalwon:
Curious as well, I mean if people can make magisk modules, should be easy to do the same way.
[Magisk] Vision:
You're right, and I think this is only if keybox.xml have 3 certificate.
[Magisk] wilsonhlacerda:
Currently not. And I doubt it.
[Magisk] dknight178:
Has anyone using stock oneplus been able to make this work?
[Magisk] thecoolkid:
I've seen some guides about resigning all the apks and framework.jar inside the build, but they were pretty old (from twenty-teens), so I don't know if Android still works that way...
[Magisk] j4imb0x:
Can you please tell me what the exact model is?
[Magisk] Vicep83:
Pixel 7
[Magisk] macacao:
Didn't you had the issue saying "BASH cannot load on this device!" ?
[Magisk] AvisAile:
You can install Bash module

GitHub - JohnFawkes/Bash-For-Android: Bash Shell Cross-Compiled for Android

Bash Shell Cross-Compiled for Android. Contribute to JohnFawkes/Bash-For-Android development by creating an account on GitHub.

github.com
[Magisk] Vision:
To solve problem with dummy boot-framework.art and the apps in MagiskHide can't open, must save .dex into framework folder or something like that and load it with PathClassLoader.

if Anyone (except @chiteroman because already answer me about this) know how to do this with PathClassLoader (can send me PM if want) ?
[Magisk] Lucius.sh:
Thank you working perfectly on SM-F731B.

Using stock ROM with Magisk.
[Magisk] bggold:
I get Modifying framework.jar failed.

Pixel 8 Pro Stock June. Magisk 27002, bash and busybox modules installed.

Log & framework.jar attached.
[Magisk] mavrovelos:
I installed the module FrameworkPatcherGO-v1.1.1 on a Pixel 7 pro, stock ROM, rooted with magisk alpha, and after this I couldn't even pass basic integrity. Uninstalling it and installing again play integrity fix(latest) I have Device integrity passing. My question is: if I disable play integrity fix I can't pass, once again basic integrity. Before installing FrameworkPatcherGO-v1.1.1 I could pass basic integrity. What has changed? I uninstalled the module completely by the way
[Magisk] IBq536XJaWThZsjwwwApTUiV:
Which other modules did you have enabled?
[Magisk] badabing2003:
Systemless hosts
[Magisk] Raz0Rfail:
You have the same error behavior as I am (I checked your install log) with CRDROID 10.5 on the Pixel 8:

Module Installation can't find bash · Issue #10 · changhuapeng/FrameworkPatcherGO

I tried to install the FrameworkPatcher v1.1.1 on my Pixel 8 with Evolution X ROM and Magisk 27.0. The Installation fails on my side because it can't find the bash binary. I have executed the find ...

github.com
[Magisk] j4imb0x:
Android 13; SM-A042M
[Magisk] changhuapeng:
I'm still working on a solution to the bash issue. For now, you can try v1.0.1.

If v1.0.1 still isn't working then you can try installing either this bash module or use this modded FPG.
[Magisk] Raz0Rfail:
Results without using bash module on magisk v27.0 (release build) the same results with magisk canary:

1.1.1 and 1.0.1 returns missing bash module

modded FPG returns directly this error:

Copying zip to temp directory

unzip error

Downloaded the file multiple times, checked SHA-256 value it's the same.

Tried to install the module with Androidacy Module Manager -> not correct bootmode.

A friend mentioned to extract the zip contents and recreate it as a new zip file with no compression.

This file could be read without any issues in magisk canary.

It got trough all steps and result was:

"FrameworkPatch set up successfully!"

Phone rebooted, but got stuck in an bootloop. I waited 5mins, but it showed only the CRDROID Logo.

After the next boot I removed the module with:

adb shell
su
rm /data/adb/modules/FrameworkPatcherGo/ -rf
reboot

Afterwards the phone started successfully again.

Then I removed the bash module and retried with the repacked modded FPG

It could successfully set up FrameworkPatch as well.

The restart again resulted in an bootloop.

Then I checked all files from Modded FPG with FPG 1.1.1 and saw the following differences:

In the original FPG 1.0.1 the binaries in META-INF\zbin are missing which got added in modded FPG.

These files are present in the FPG 1.1.1 Version. But these files have a different size!

Then I checked every file between FPG 1.1.1 and modded FPG and saw some difference in the file

META-INF\com\google\android\magisk\func.sh.

In modded FPG these functions are added in the beginning of the file:

if [ -f "/data/adb/magisk/busybox" ]; then
unzip() { /data/adb/magisk/busybox unzip "$@"; }
wget() { /data/adb/magisk/busybox wget "$@"; }
elif [ -f "/data/adb/ksu/bin/busybox" ]; then
unzip() { /data/adb/ksu/bin/busybox unzip "$@"; }
wget() { /data/adb/ksu/bin/busybox wget "$@"; }
elif [ -f "/data/adb/ap/bin/busybox" ]; then
unzip() { /data/adb/ap/bin/busybox unzip "$@"; }
wget() { /data/adb/ap/bin/busybox wget "$@"; }
fi

I have added these functions to the functions.sh in the 1.1.1 version.

The other files have some minor changes which I didn't changed.

Then I build an zip file and got again the message that the bash binary is missing.

After that I replaced all the META-INF\zbin binaries from the mod FDG in the 1.1.1 FDG version.

Then It worked and I could go trough all steps with my modded 1.1.1 version.

The Installation was successful again, but it resulted again in an bootloop :(

Attached is my modded 1.1.1 version and the logs.

An last point what I have is the following:

When using the bash binary, the apktool Version is 2.9.0 and it can't recompile the framework.jar so the process fails.

With the modded version the apktool version is 2.7.0 and it can compile the framework.jar
[Magisk] Raikusu17:
Hey man, amazing work you're doing here! I tried this with my Lenovo y70 on a stock-based rooted ROM (Zui 14.0.808) running Android 12. The problem is every time I flash the framework module, after reboot, it looks like the system file manager breaks and keeps shutting down apps that use it like File Manager, Zarchiver, mt manager, and even Magisk Kitsune when trying to flash another module. Does this module not work specifically with my device?

I even tried when I was using custom ROMs like FLymeOS on Android 13 and Alphadroid on Android 13 as well. I just downgraded to Android 12 as I thought it was the issue. But still the same results. What do you recommend I do next? By the way, I also tried ver 101 and 100.
[Magisk] JazonX:
How to test whether "TEE" is broken or working ?

EDIT: Got the App

Release v1.6.0 · vvb2060/KeyAttestation

Contribute to vvb2060/KeyAttestation development by creating an account on GitHub.

github.com
[Magisk] Kraiwit007:
I have to install Bootloader Spoofer to open KeyAttes, is that mean my TEE is broken
[Magisk] JazonX:
Run without the spoof to test the actual status.

You're seeing a spoofed - otherwise a made up / incorrect status.
[Magisk] Lu5ck:
There's a rom resigner script in github, not sure if it works for A14 though.
[Magisk] thecoolkid:
Can you paste a link?
[Magisk] jakell888888888:
@chiteroman@changhuapeng

After another four hours, my device was banned by Google. It was all green before and is now recognized as shown in the picture.
[Magisk] Vision:
Yeah, Google fixed.

For BASIC and DEVICE, go back to 15.9.9 or PIF Fork.

P.S If you can add smaller image to take less space.
[Magisk] Lucius.sh:
Yes.

Can confirm my device is now MEETS_BASIC_INTEGRITY only.
[Magisk] Vision:
Yeah, Google fixed.

If you read the last pageσ of PIF thread, explain about it.
[Magisk] Lu5ck:
GitHub - ybtag/ROM_resigner: Python Script to resign an Android ROM using custom keys

Python Script to resign an Android ROM using custom keys - ybtag/ROM_resigner

github.com
[Magisk] changhuapeng:
Like you've found out, the update from v1.0.x to v1.1.x has some bug fixes for these long-standing issues that wasn't fully resolved as I'd hoped.

Thanks for the detailed summary and the log!
[Magisk] 0b946122bf4bee8d3e9748122:
If what you have is still valid, I'd love to get my hands on it :)

Doing some testing on a few of my devices right now, but I don't have a non-revoked keybox available.
[Magisk] David B.:
I asked to try it earlier in this thread and he ignored me. 😆
[Magisk] sampei:
Do you have Mixplorer? if you have then you can try decompress my modded zip and compress to zip.

When you compress to zip you need to select META-INF, customize.sh and module.prop. not a parent folder.

Sometimes it works.

Anyway I attached Zip hash here.

CRC32: 53ddcca5

MD5: 14df2deff23e46477ced134ab1150dc1

SHA1: 010fa3102e3937738ed371c83c55cd01711672ad

SHA256: 1f18aa984d3e63fcf65fe8fb3e7e1371dbfaa5b2275bb0dd4850e21d27b34948

SHA384: f3c79008159dca1bcf52709e3505555be2abb0622a0e7c04ea60ca5e915e3a2b661be7f33a31b40b0dfe193ca6e10cdc

SHA512: 2aa228537cfc053f17e31a7f2f09e5278b5982c74af026508a6f93f39ab6649e766b43d0880cf8de7de87978f3fe0f3a031ad905dc7bb37742839909a219c383
[Magisk] yjcbn:
Can we have a simpler process for compiling our own `class.dex`?
[Magisk] Vision:
Unfortunately until now the easy way, is with Android Studio.
[Magisk] Captain_Throwback:
I think using Github Actions is easier actually.
[Magisk] Vision:
I didn't know that.

Thanks for info. I appreciate.
[Magisk] badabing2003:
Indeed, but the whole point of building your is to customize it so that you can have your own print or keybox.

And you don't want that to be public.

I don't know if cloning the repo and making it private would violate the license or not, but I'll leave that exercise to people who want to build it with GitHub actions.

It's not really that hard to build it with Android studio, you just need to install it, don't even need to run the gui, just couple of command lines and you have a build.
[Magisk] changhuapeng:
GitHub Actions really helps to streamline the whole building process but it still requires some basic knowledge to set it up.

For people who need hand-holding, I personally think that Android Studio's GUI are still the most straight-forward and simplest, with just the push of a few buttons. Besides, there are also plenty of video/text tutorials online regarding Android Studio to guide these newbies along.
[Magisk] Captain_Throwback:
Not if they just fork your repo, since you've set it up so nicely already ;)

At any rate, I've built it both ways, and it's not terribly difficult either way.
[Magisk] changhuapeng:
Honestly, that will still require them to understand the set up and triggers to start the Actions and they'll probably ask for an even simpler method. :LOL:
[Magisk] mkcs:
Installed and boot successfully, however, play integrity checker crashes immediately. Btw, without a leaked keybox, this module cannot pass strong integrity?
[Magisk] Vision:
Disabled all other modules, except this.

Yeah without can't pass Strong.
[Magisk] mkcs:
I disabled all other modules such as ZygiskNext, but no integrity is shown:(
[Magisk] Vision:
You need PIF fork script-only-mode and add to MagiskHide/DenyList or whateven you have the gms.unstable.

Or try Shamiko.

and read this page: https://xdaforums.com/t/module-framework-patcher-go.4674536/page-10
[Magisk] mkcs:
Still no integrity. It seems Shamiko has conflicts with this module. SPIC would not respond and other PI checkers would crash if I enable Shamiko. I attached what I enabled besides Framework Patcher Go, gms and gms.unstable are on the denylist.
[Magisk] Vision:
Interesting.

Read this page: https://xdaforums.com/t/module-framework-patcher-go.4674536/page-10
[Magisk] mkcs:
Another interesting observation is that with Magisk(27001) built in Zygisk enabled + FP Go + PIF (script only mode), TB checker would crash, where Zygisk-Next wouldn't but gives no integrity response. Denylist already included gms and gms.unstable.
[Magisk] Vision:
Because I had try, Magisk latest canary with this and shamiko and DenyList gms.unstable, and all the info from the page I write you, and work for me.

EDIT: Maybe your framework.jar not patch correctly 🤔
[Magisk] boteomap2:
I manually use framework patch to patch my framework.jar custom ROM. I'm using built dex in chiteroman repo and edit only engineGetCertificateChain to get spoof lock bootloader. But unfortunately, my device stop at mi logo and can't go to hyperos logo. How can I fix it?
[Magisk] Vision:
Dummy the boot-framework.art via Magisk module.
[Magisk] boteomap2:
I flashed old framework to boot my phone again, where is the location i can get that file?
[Magisk] Vision:
For me on A11 is in /system/framework/arm64 and arm.

Read the last: https://xdaforums.com/t/android-13-decompile-and-recompile-framework-jar.4602085/#post-89516917
[Magisk] boteomap2:
Can't any found boot-framework
[Magisk] Vision:
Go manually to this location, /system/framework/arm64
[Magisk] boteomap2:
Forgot to tell you, i check /system/framework/ folder before run command, there is no folder, no boot-framework, only have jar files. And i also run that command with /system/ path, but got no result
[Magisk] Vision:
Which Android you have and rom?
[Magisk] mkcs:
It's strange as there's no error during the installation for all yes options in the latest release😶
[Magisk] boteomap2:
Rom hyperVN, android 14 on device xiaomi13.

The framework.jar already has 6 class.dex, so i rename it to classes7.dex

Don't know if possible too many dex lead to boot stuck
[Magisk] Vision:
Interesting 🤔

Oh, after A12+ the boot-framework.art is already dummy.

Understand, I don't think so 😕
[Magisk] boteomap2:
I can boot now, maybe too many dex, so i import smali to the current dex and it boot now. But the device still not spoof lock bootloader. Is anyone face this issue before?
[Magisk] Vision:
The frameworkpatch method updated before some days, maybe the info not ? 🤔

EDIT: Why not try the PIF v16.3, you can add your pif.json and keybox.xml
[Magisk] boteomap2:
I also tested with old dex before update (changhuapeng fork repo) but still not working.

My only target is spoof bootloader, is the PIF matter in this case? I also tried disable all module and got no luck

Maybe the problem is my custom ROM...
[Magisk] Vision:
Oh understand, with the PIF still say BL is unlocked, but send the value to DG.

Why only spoof Bootloader? Without pass 2/3 ?
[Magisk] boteomap2:
Just for testing purpose, i'm using PIF 15.9.9 can pass 1/2, but that testing app still saying bootloader unlocked, and also there is an app i got block because that app still detect my phone unlock bootloader.

I can bypass it easy with lposed module...but yeah, i'm doing this for learning
[Magisk] Vision:
PIF v16.3

Oh for that, because lot apps need only to pass 2/3 that mean the app think you have BL locked.
[Magisk] boteomap2:
Let's me clarify, i passed device and basic check with PIF 15.9.9 but the app still detect bootloader unlock. So i need to use lposed module SpoofingBoolader and it work

My friend said this framework patch can make that app can't detect bootloader unlock too (he tested on stock rom) so that's why i'm here but got no luck 😅
[Magisk] Vision:
Oh now understand.

Yeah with frameworkpatch method all the apps detect as BL is locked

Me too all stock with Kitsune Mask.
[Magisk] xk3v1lx:
I changed my rom to PE A13

I just install Magisk Alpha and Shamiko

Then, i must add Gms and Vendor to Denylist or not?

Thanks ❤️
[Magisk] toolhas4degrees:
How do I fix this
[Magisk] Vision:
Have you try this?

GitHub - JohnFawkes/Bash-For-Android: Bash Shell Cross-Compiled for Android

Bash Shell Cross-Compiled for Android. Contribute to JohnFawkes/Bash-For-Android development by creating an account on GitHub.

github.com

Or this ?

[MODULE] Framework Patcher GO

Framework Patcher GO Based on chiteroman's FrameworkPatch, this module modifies framework.jar directly on the phone, to build a valid system-level certificate chain. This module is compatible with Magisk, KernelSU, and APatch. For more details...

xdaforums.com
[Magisk] toolhas4degrees:
No module download on the first...
[Magisk] Vision:
Click code-> Download zip, after get all the files and zip it and can flash via Magisk.
[Magisk] toolhas4degrees:
Got bash working. Fails at modifying framework jar.

Edit nevermind. I used the arm v8 and had to repack it as it had an unpack error and that worked.

But no integrity is obtained. No basic or device

Thanks for all your help.
[Magisk] jakell888888888:
sorry I was too eager
[Magisk] changhuapeng:
The framework.jar will be in the directory where you entered your command from: "C:\Program Files (x86)\Minimal ADB and Fastboot"
[Magisk] Usama-CW:
Thanks, found it. i sent you on xda
[Magisk] Usama-CW:
I am using unofficial los 21 from marcos which offers strong integrity. But my tee is broken, i heard that if i fix my tee original keys will be gone and i no longer pass strong on global rom with bootloader locked
[Magisk] changhuapeng:
Yeah, reprograming your broken TEE won't guarentee that you'll pass STRONG integrity so that's really not worth getting yourself that risk.

Framework Patch, which my module is based on, as well as the ROM that you're using, are both written by marcos. So it is integrated into your ROM already and you do not have to use my module. From going through your framework.jar, I've also confirm that the integration are there.
[Magisk] Vision:
Yeah, unfortunately bad new for broken TEE (if want lock again BL).
[Magisk] Vicep83:
Hi, on Pixel 7 Android 14, Key attestation app shows the messages "AOSP software attestation root certificate Private key of attest key is well known, the certificate chain can be tampered with." "Bootloader is locked", and I can't take screenshots or photos no more and the device seems pretty unstable
[Magisk] Vicep83:
*With classes.dex provided by captain
[Magisk] Vision:
As I understand, you make the process with Framework Patcher GO and put inside the classes.dex by captain? And with latest (ApplicationPackageManager.smali) option or not?
[Magisk] Vicep83:
Yes and yes with the option
[Magisk] Vision:
Interesting, you have tried manually the method with frameworkpatch? Because on A14 have more success, you have all stock?
[Magisk] Vicep83:
No bro I don't have the knowledge to do it, i'm not even sure if the result that I have on key attestation app is the one expected with this module, maybe this is necessary to pull with the real classes.dex from my device ? Yes stock rom with kitsune
[Magisk] Vision:
Understand, yeah the results, is right, the same I have, besides the can't screenshot and pretty unstable, what you pass?

And this with dex, this modules the real classes.dex, decompile and compile with the extra classes.dex by frameworkpatch.
[Magisk] Vicep83:
I pass only Basic, and the other apps like Momo or Native still shows bootload unlocked
[Magisk] changhuapeng:
You are getting the expected result with that root certificate as well as the spoofed locked bootloader. Besides that, your device should be also passing DEVICE integrity. These are the from keybox and fingerprint hardcoded in the classes.dex which are being used in Framework Patch.

While most people haven't really faced any issue after installing this module, there are some like you who saw instabilities in their devices. Some others have also encountered bootloops, app crashes or system becoming sluggish, and these results are not uncommon when patching or mounting system files. So, I would say that this is the limitation on my module as compared to other bootloader or fingerprint spoofing methods like PIF or BootloaderSpoofer.

I have observed that clearing device dalvik-cache would sometimes solve these issues so you can probably try that first to see if it works. If not, you can send me your patched framework.jar file that is in the /data/adb/modules/FrameworkPatcherGo/system/framework directory and I can look if the codes are correctly being patched.
[Magisk] Vicep83:
Thank you for your help and your work on this module, unfortunately , clearing dalvik cache did not solve the issue, wich seem to be that device have difficulties to read/write data on storage when your module is installed, and for the framework file, here it is