yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ze7zez:
The first active installation seen on the web is probably yours I believe.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
About 3 or 4 months ago, that site was done for 2 or 3 weeks. When it came back up around 5 weeks ago, the stats are all made up. It's like they values were made up instead of being all reset back to 0. Also, I believe there was a feature to see the actual name of the string and date build and that seems to be gone as well? Or I'm not smart enough to find it.

Good job @lifehackerhansol on getting 20 official + your contributions on gerrit. I know that's outside my skill set. It will look good on your resume for future jobs.

Good job getting 21 up and running. Before March 5, 2024 security patches (aka QPR2), I had most of my legacy devices on 21, but afterwards, there's 3 platforms that have boot problems now.

I have one SM-T290 where I can install LineageOS and the other has the updated bootloader (purchased used from a seller who upgraded the OS and bootloader) so I'm stuck on stock or GSI on that one.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lifehackerhansol:
Stats were kind of messed up before the funny reset that happened; a lot were being faked etc (like there was a million installs for sagit at one point which makes 0 sense realistically). It does some rounding stuff now that I'm not sure how it works.

To be honest it's a miracle that this tablet is still alive, every day I think about throwing it out of my window LOL
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] xperiazu21:
It's good to see that this device still has Android 14 support. It's really slow though. 🤣

My SM-T295 was successfully installed and no major problems were found after a simple trial.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
Hey there lifehacker! I was hoping you could point me in the right direction on something. I'm trying to compile the kernel by it's self and I've spent the last day or so trying and researching, only to have it fail. I've tried running the two build_kernel scripts with the def_linage_gtowifi config, both as an argument and just copying the config to .config. Also running make as stated in the directions(that are for kernels in gerneral) and a 100 different other ways. I'm trying to make a kali nethunter kernel and perhaps ultimatly a full port if possible but it just won't compile any way I try it. It ends the same way wether I try to build just the kernel or through the kali program.

I end up with it saying an unknown expression: 28 and the next line is the same with 29. If I can get it to run for a minute it errors with a syntax error in the sched.h file about LD_CPU has too many cpus or something. I feel that I'm just not running the right command or something since I have successfully compiled a working image of lineage 21 and flashed it to the device. It works, It's awesome and thank you for your contributions to us!

I've tried building from my lineage tree that I compiled and just standalone cloning the kernel git repo.

I read on aosp that the latest android didn't support build.sh scripts but instead use a tool called bazel? It wasn't where it was supposed to be in the source so is that something I need to investigate more? Any help is appreciated!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lifehackerhansol:
Hello,

LineageOS 21 now officially supports gtowifi. As a result, my unofficial builds are discontinued.

Please head to the usual thread: https://xdaforums.com/t/4535635
[Redmi Note 12 4G] larina3315:
The recently released RN13 4G sapphire is virtually identical to RN12 4G topaz/tapas, just with a different camera and fp sensor.

They are similar to the point that OrangeFox recovery's tapas/topaz build, completely unmodified, runs on sapphire in a fully functional way, albeit with a minor issue with screen timeout.

Unfortunately, the RN13 4G sapphire has not had much developer interest, to the point where even many months after it's release there still isn't a XDA page for the device, let alone any official recoveries or reputable Custom ROMs.

Thus, I would like to humbly request the devs of tapas/topaz to kindly take a look, and consider porting or creating unified builds of ROMs for sapphire.

And if any resources are needed (e.g. firmware files and/or other vendor resources) then I will be more than happy to provide them.
[Redmi Note 12 4G] DarthJabba9:
For information, the OrangeFox "unified" topaz beta just released today now supports sapphire without any screen timeout problem.
[Magisk] Captain_Throwback:
Question for you - is there any reason that you couldn't just include the FrameworkPatch-compiled classes.dex in the zip by default, if people just want to use this module to achieve Device Integrity without the need of PIF or Zygisk?

It seems that this could be a viable alternative to PIF for people that have apps that detect Zygisk. Since it's also dependent on a working fingerprint, it could easily be recompiled when the current fingerprint no longer works.

Just a thought, since I think in most cases, achieving Strong Integrity with FrameworkPatch isn't possible. At the very least, it could be included as the default, so it's a simple flashable zip, and if people want to try a different keybox or fingerprint compiled with FrameworkPatch, all they would have to do is replace the included classes.dex.

EDIT: Since I have this post here, I thought I might just upload the classes.dex files here myself, so @changhuapeng doesnt have to worry about it, and it'll give the less-technical users an easy way to try this mod (and hopefully provide additional feedback if it isn't working as expected/intended).

These classes.dex files are from a straight compile of the FrameworkPatch source, with whatever fingerprint and keybox are included therein. I will try and update this post as needed with a new classes.dex if the fingerprint or keybox are changed.

EDIT 2: Removed attachment - see FAQ 2 above
[Magisk] Spartacus500:
Does this module work on Samsung Rom without modifying the framework.jar file ?
[Magisk] changhuapeng:
I could include the compiled classes.dex by default but that would be the keybox and fingerprint that are provided by @chiteroman in his Framework Github and I can't make sure that they are always up to date so users will still have to compile the classes.dex themselves if those aren't working.

A major problem about this module that I had foreseen is that there is no one-size-fits-all way to patch all the different ROMs and Android versions out there and that's the main reason I'm apprehensive about releasing this module at first. I'm expecting the bulk of my work to be on improving the module's compatibility, so I don't really want the extra workload on maintaining keyboxes and fingerprints.

At the moment, my module has removed the major hurdles about Framework Patch, and it's simple enough for users to know if their keybox or fingerprint are up to date by compiling the classes.dex themselves in Android Studio. So maybe until I have come up with a more seamless way to include up to date classes.dex, I'll let the users be responsible for that and focus on the other work that needs to be done.
[Magisk] changhuapeng:
I have no idea if it's working or not until you try it out. This module will do the modification so you don't have to do it yourself at all.
[Magisk] Spartacus500:
Ok, not working install on Magisk 27.0 🤷
[Magisk] yoohoo55:
its has been error. showing that

View attachment 6109059
[Magisk] Captain_Throwback:
How did you build your classes.dex?
[Magisk] changhuapeng:
Can you test this test version if it's working on your device?

@Captain_Throwback can you try if this version is working on KernelSU?

Edit: test zip removed
[Magisk] changhuapeng:
Do you have the installation log?
[Magisk] Captain_Throwback:
I'm using APatch presently, but the install fails nonetheless.
[Magisk] Spartacus500:
Same error install 🤷
[Magisk] Captain_Throwback:
I understand.

Since I have the 2nd post here, I decided to upload the current classes.dex, in case some less-technical people want to try this mod, to provide a bit more broad feedback on whether it's working and if any modifications are needed. Hopefully that's okay, but if not, let me know and I can take it down.

If you have an issue with the installation of the module, please save the log from the root manager app, and upload it here along with your device's unmodified framework.jar. That will help @changhuapeng to troubleshoot any issues and provide test builds to try and fix them.
[Magisk] changhuapeng:
Thanks, I have no problem with that.
[Magisk] changhuapeng:
I can't reproduce the error on my device with Magisk 27.0 installed.
[Magisk] Usama-CW:
What this means?

"Leaf certificate register not found in engineGetCertificateChain method"
[Magisk] changhuapeng:
I've just fixed a bug and released v0.2.3 that may have fix the error that you encountered. Please try it.
[Magisk] Usama-CW:
using this dex file
[Magisk] changhuapeng:
Can you provide me your framework.jar? You can extract it from your device by enabling USB debugging in developer options, connecting your device to your PC and entering this on your PC terminal:

adb pull /system/framework/framework.jar
[Magisk] Usama-CW:
i cant find it on my pc where its pulled?
[Magisk] Vicep83:
You have device integrity ?
[Magisk] Vision:
Basic, but before can't get even basic.

I write this for the rest of users, who already get device.
[Magisk] Captain_Throwback:
I'll test this with Scripts-only mode on PIFork, as the result should be the same. I had already tried with just Sensitive Props, but never tried to hide gms.unstable, which should've been obvious. That would probably explain why just using PIFork works, as the hiding is part of the Zygisk mod, besides the prop spoofing.

I'll report back as soon as I get home and can test.
[Magisk] Vision:
Yeah exactly, now must take this and ported without zygisk, and yeah I remember older device without hardware, can pass only by hide gms.unstable and with all this together.

Voila.

EDIT: With Scripts-only mode on PIFork and GMS.unstable is the same, but still with dummy the boot framework.art via module in my device have the problem when I have a app in MagiskHide, the app crash when go to open.
[Magisk] Captain_Throwback:
This was the missing piece. Added gms.unstable to MagiskHide and reinstalled PIFork in Scripts-only mode, and now I'm passing Device Integrity as expected, without the need of Zygisk. Thanks for the reminder!

P.S. Device still shows certified in Play Store, too, so it seems that now everything is working properly.
[Magisk] changhuapeng:
Nice! So my hunch was right about osm0sis's service.sh and post-fs-data.sh scripts being the finishing touch. It's just like osm0sis has specially prepared PIFork for this because you don't even have to add gms.unstable to the denylist while in scripts-only mode, since he does that in his script already.

Edit: I stand corrected, was confused with MagiskHide and DenyList.
[Magisk] Captain_Throwback:
But again, like I said in my first post about this, Scripts-only mode results in No Integrity without the addition of gms.unstable to MagiskHide.
[Magisk] badabing2003:
Does it still work with Zygisk enabled? of one has other modules that require zygisk to be enabled?
[Magisk] Captain_Throwback:
Yes, Zygisk can be enabled and everything still works fine.
[Magisk] sampei:
it seems like the original busybox, bash, aapt makes error for our device....I'm trying to figure out it... and zip exec also got error
[Magisk] sampei:
Try this. All binaries that had errors were swapped.
[Magisk] yhs0331:
still error
[Magisk] changhuapeng:
PSA: FrameworkPatcherGO uses a third-party installer package that contains required binaries and scripting functions, but it looks like the installer is not being maintained any more and is causing errors for some users that I'm unable to reproduce.

For what was used to be a project for my personal use, I don't really have the spare time to rewrite FPG to truly resolve these compatibility issues and to get it off its dependency on this unmaintained installer. I cannot promise you anything but I'll continue to slowly chip away at the issue when I have the time. So if anyone has any solutions in the meantime, you can send in a pull request at FPG's GitHub.

For now, anyone facing issues with binaries during installation can try out this zip that @sampei has kindly put out with the affected binaries updated.
[Magisk] sampei:
Try this. All binaries that had errors were swapped.

I recompiled zipalign so should be fine.
[Magisk] yhs0331:
This is OK. Thank you very much.
[Magisk] Stillhard:
Look here, released new update as per-today
[Magisk] changhuapeng:
Thanks for the heads up! I have contacted the developer regarding the issues encountered.

I will update the module with the new updated installer soon.
[Magisk] Xennet:
@changhuapeng

Is it possible to delete the keybox entry while compiling the classes.dex file if we don't have a valid keybox file and need this only for passing device integrity...as if we use the default keybox it is a way of getting detected by apps as a revoked attestation key being used...
[Magisk] changhuapeng:
No, don't do it. You will likely face bootloops if you do that.

If you don't want to spoof bootloader with FrameworkPatch then go into my module META-INF/com/google/android/magisk/customize.sh script and remove the section that patches AndroidKeyStoreSpi.smali.
[Magisk] Vision:
To solve problem with dummy boot-framework.art and the apps in MagiskHide can't open, must save .dex into framework folder and load it with PathClassLoader.

if Anyone know how to do this with PathClassLoader (can send me PM if want) ?
[Magisk] jakell888888888:
This is my file. I cannot install it as shown. Please help me compile it so that I can install it. Thank you. I would be very grateful, this problem has been bothering me for a long time.
[Magisk] jakell888888888:
Error reminder
[Magisk] Vision:
Can you have try this specific version?

[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] AvisAile:
This doesn't work for me (Pixel 8 - Android 15 and magisk 27002)
[Magisk] Vision:
Neither the original version?
[Magisk] AvisAile:
It's say me that I don't have BusyBox and if I install a BusyBox magisk module, it's say me that I don't have Bash on my device ...
[Magisk] Vision:
Oh you have the issue, lot of users say.

Now must waiting for this:

https://xdaforums.com/t/module-framework-patcher-go.4674536/post-89562800
[Magisk] changhuapeng:
Can you give me your device model and also the installation log?
[Magisk] changhuapeng:
Don't get your hopes high.
[Magisk] Vision:
Yeah, I read it here.

Still your module save us, from a lot of work. We appreciate.

[ZIP - Dual Installer] Dynamic Installer Stable 5.0-b [ Android 10+ or earlier ]

SUPPORT: TELEGRAM CHANNEL - TELEGRAM GROUP - SUPPORT ME ABOUT THIS: With this you can make Automatic Installers (.ZIP flash files) for All Android devices without limitations (Supports an installation from Recovery or can be used to create a...

xdaforums.com
[Magisk] chiteroman:
That's another way but I can't guarantee you that it will solve your issues.
[Magisk] Vision:
You have write me this.

I have try some mods (including /system/etc/boot-image.bprof) to add the classes5.dex and no need anymore delete the .art, but not work, and this or if exist another way, to pass and to have apps in MagiskHide.

EDIT: And really thanks you for all your hard work. I appreciate as always.
[Magisk] AvisAile:
Pixel 8 :)
[Magisk] jakell888888888:
I have the same tip! I can't use it.
[Magisk] David B.:
If the offer is still open, please DM me. I would be interested in giving it a shot. I am trying to get this module working on my Pixel 3 XL running the June 11 build of LineageOS 21.
[Magisk] Vision:
For bash maybe this do the job.

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] AvisAile:
I unzipped it and re-zipped it, and managed to install it ! Thanks
[Magisk] Vision:
That's is good 👍
[Magisk] Vision:
[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] casouzaj:
I've given FPG one more try, now disabling PlayIntegrityFork, Zygisk Assistant and ZygiskNext. This way, I don't have the 'media picker' constant crashing bug, but I don't pass the device integrity test. Moreover, Momo detects, besides the usual 'Device is running custom ROM' and 'TEE broken'', also 'Found Magisk' (I don't use magisk for weeks!), 'Partition mounted abnormally' and ''Bootloader unlocked'. After disabling FPG and re-enabling the modules previously disabled, device integrity is back, and Momo is displaying only the first two outputs I described before. See screenshots below.
[Magisk] jakell888888888:
Can you tell me how you did it? I still can’t use it and I get the same prompt that I can’t install it.
[Magisk] badabing2003:
What device?

Did you set the PlayIntegrityFork in scripts-only-mode ?
[Magisk] casouzaj:
Sony Xperia 1 II, running LineageOS 21, rooted by KerrnelSU.

No, because when I enable Zygisk (Next), I get the 'media picker' constant crash bug.
[Magisk] badabing2003:
Is it a zygisk issue or zygisk next issue?

Does it work with Magisk?
[Magisk] Captain_Throwback:
Scripts-only mode doesn't require Zygisk.
[Magisk] casouzaj:
Yes, I found out, and I got bootloop after activating it. S**t!
[Magisk] Vision:
You mention to @AvisAile

I only said, for bash maybe this do the job.

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:
Yeah understand, this need a valid keybox.
[Magisk] changhuapeng:
Thanks! Can you test release v1.1.0 and see if it works?

Please try release v1.1.0 release v1.1.1. This module will never give you STRONG integrity, not unless you have an unrevoked valid keybox.
[Magisk] AvisAile:
Without BusyBox module, It's say me that I don't have Bash. If I install Bash module, i got "Error : keycheck"
[Magisk] changhuapeng:
Sorry, I'm a little confused. So for this installation log, there is no extra busybox and bash magisk modules installed, right?
[Magisk] AvisAile:
Only bash module
[Magisk] changhuapeng:
Anyway, the "Error : keycheck" was a mistake on my part. Thanks to you, this keycheck mistake is fixed.

Is this the bash module that you have installed?
[Magisk] xk3v1lx:
My rom used is crDroid A10 (polaris - mix2s xiaomi) have a testkey check (not signed 😖)

I contact my Dev and they said NO LONGER SUPPORT

please help me to patch my rom simply to pass my Play Integrity ❤️ Thanks a lot
[Magisk] Vision:
Wrong thread.

You can check here https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/ have discussion about this and can Google it.
[Magisk] changhuapeng:
There's only 3 options available that you can do:

Build the ROM from source and sign it

Look for and switch to a different ROM that is already signed

Go back to stock ROM and lock your bootloader

Choosing either option 1 or 2 will still require you to have a working fingerprint, or rather, fingerprints to use with PIF and I don't see a light at the end of the tunnel to this approach.

Edit: Forgotten about PIF at stock ROM
[Magisk] xk3v1lx:
Thanks for your support ❤️

But i don't wanna do all 3 your options because i don't wanna change my rom 😖
[Magisk] chiteroman:
crDroid.net - Download crDroid v7 for Mi Mix 2s (polaris)

official crDroid v7 for Mi Mix 2s (polaris)

crdroid.net

Is this your ROM ?
[Magisk] trevtdogg:
you don't need to lock bootloader just because you go back to stock rom.
[Magisk] xk3v1lx:
No, sir

Mine is 6.5
[Magisk] jakell888888888:
I successfully flashed the module, but just like you said I still can't play the game and still can't pass strong verification. I'm going to ask if I can find a valid password bucket for my phone~
[Magisk] jakell888888888:
@changhuapeng I asked some of my friends who work in Huawei's mobile phone security department or vivo's mobile phone system security department. They pointed out that it is impossible for all manufacturers to leak valid keys. So, everything I have done so far is In vain, but thanks for the module.
[Magisk] pndwal:
Context was 'options to meet DEVICE-INTEGRITY'... 😉 PW
[Magisk] trevtdogg:
I'm on stock rom, unlocked bootloader and have device integrity.
[Magisk] changhuapeng:
Thanks for the correction. Using PIF at stock slipped my mind, and maybe a little brain fogged thinking it's strong instead of device integrity that he wanted.
[Magisk] changhuapeng:
That's if it's 'options to meet device integrity by default', there's a option of using PIF at stock too but it slipped my mind.
[Magisk] changhuapeng:
Thanks for verifying that the update fixed the issue for you. Yeah, there's no easier way to pass strong integrity than to simply have a locked bootloader.

If the game is not resource intensive, perhaps you can get a cheap phone and keep it at stock just for the game. Some people are doing the same for their banking apps.
[Magisk] pndwal:
Me too!...

mmm... Thought you had it covered in 2), switch to signed ROM, and 3), restore stock/locked was just the last resort... Guess it's just how we think/read. 🤷 PW
[Magisk] vygavedha:
@changhuapeng

After unlocking my BL and rooting with magisk , passing basic and device integrity with PIF ,Netflix is not opening.

Will this module fix my issue with BL.

I am attaching DRM key details after unlocking BL
[Magisk] Aarif goku:
Looks like default classes.dex removed and download failed.

edit: worked after changing network. my isp was blocking it.

Did not pass basic/device integrity on signed Los on my moto G32.
[Magisk] RAZINARES:
Passing Strong Integrity💪

Stock ROM + KSU

Device: Pixel 7a
[Magisk] Vicep83:
Do you have valid keybox ?
[Magisk] RAZINARES:
Nah, the module did everything for me 😅
[Magisk] Vicep83:
How is that possible bro ? 😅
[Magisk] chiteroman:
Really? With default keybox?
[Magisk] RAZINARES:
Yeah
[Magisk] chiteroman:
Yes, Strong passing, they touch something

Play Integrity Fix

HOLY ****, GOOGLE WHAT YOU DO HAHAHAHA STRONG PASSING WITH SW ATTESTATION CERTS

t.me
[Magisk] Vicep83:
Lol 😂
[Magisk] iTudorS:
I can't get it to install, first it says bash is unavailable, tried to install the bash module from this thread, it says unzip failed :(

pixel 8 pro latest update
[Magisk] Vision:
Google already has a fix for it? Pass 2/3 😂🤣
[Magisk] Vicep83:
You must uninstall pif and flash shamiko
[Magisk] Isa Daud:
Hi, seems legit. may i know please.. what's minimum android version to run this awesome module?

Thanks in advance
[Magisk] badabing2003:
Maybe with Sailfish, (haven't tested Sailfish) but only passes device with a private print.
[Magisk] iTudorS:
managed to start installation but it won't complete, I guess doesnt work on pixel 8 pro :(

attached framework.jar just in case
[Magisk] chort123:
Failed to install on HyperOS 1.0.8.0

Poco x3 Pro
[Magisk] changhuapeng:
TO THE INFLUX Of PEOPLE COMING HERE FOR STRONG INTEGRITY: READ THIS

Those of you who are failing on v1.1.1, try v1.0.1 or read the FAQ in the OP.
[Magisk] b0l5:
Install fine, but bootloop. Oneplus 8 Pro Android 13
[Magisk] Vision:
Can't get shamiko, I have Kitsune Mask.

I have PIF fork script-only-mode.
[Magisk] Web_E:
If I understand correctly, this module is only valid for devices which comes with Key Attestation ?

I have One Plus 8 which does not support key attestation.
[Magisk] chort123:
I've tried version 1.0.1