[Mod] Secured ScreenShot Mod for K20Pro Rom - Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and

Hello Guys,
We know, Some App in Our Devices doesn't allow us to Take ScreenShot.
and We See an error saying "Couldn't Take Screenshot" OR Similar.
I'm Creating This Post Because I haven't Found Any. (I'll try to make it Up to date, Specially for whichever ROM I'll be Using in the Future).
So I Made a Magisk Module using The Smali Patcher
It will allow the User to Take ScreenShot in Protected Apps.
Just Flash it From MAgisk and Enjoy
Currently Only Available for Xiaomi EU Beta 21.5.12 ROM
Download Link:- Click Here
If you Want to Make For Your Device/Rom, You Can Use Smali Patcher,
Follow The Instructions from The Post. Click Here.
Please Comment Down for Issues OR Suggestions.
You can Contact Me on Telegram @itspdp
Click on That Thank Button, If It was Helpful.

Thanks, interesting
I remember I encountered an app or two not allowing screenshots - but I forgot now, can you please tell which apps to test with
Btw, I have Mi 9T (not Pro) and Xiaomi.eu 21.5.20 (davinci was 'delayed' a week later than your raphael), but I think the module should work as well
Btw, as I can see, changes should be systemless, hence if anything goes wrong just disabling the module (and reatarting the phone) should be enough to go back to 'normal'

Y
zgfg said:
Thanks, interesting
I remember I encountered an app or two not allowing screenshots - but I forgot now, can you please tell which apps to test with
Btw, I have Mi 9T (not Pro) and Xiaomi.eu 21.5.20 (davinci was 'delayed' a week later than your raphael), but I think the module should work as well
Btw, as I can see, changes should be systemless, hence if anything goes wrong just disabling the module (and reatarting the phone) should be enough to go back to 'normal'
Click to expand...
Click to collapse
Yes Everything will be Systemless, we can try, if anything goes wrong we can remove that module (Even from Recovery)
Use The Smali Patcher to Make Modulw for Your Device.
(Link and Tutorial already inside the post),
It's easy and will take about 5-10 minutes only.
P.s. :- This Module is Device and Rom (Including Version) Specific, You Have Make For Your Own Rom/Device amd Update it with Each OTA Update of Your Rom.

After some troubles with the PC, I was able to run Smali Patcher to create a module for my Mi 9T, Xiaomi eu 21.5.20 - do you know please a (system) apk in Xiaomi.eu that does not allow screenshots, that I can test with and without the module, to check does it work

zgfg said:
After some troubles with the PC, I was able to run Smali Patcher to create a module for my Mi 9T, Xiaomi eu 21.5.20 - do you know please a (system) apk in Xiaomi.eu that does not allow screenshots, that I can test with and without the module, to check does it work
Click to expand...
Click to collapse
Try Chrome incognito mode

ca_guri01 said:
Try Chrome incognito mode
Click to expand...
Click to collapse
Thanks, I tried Chrome Incognito window with the my Smali patch module disabled and it complained that screenshots are not allowed
I enabled the module, rebooted and tried again, and it successfully made the screenshot
Thanks, it works (Mi 9T, Xiaomi.eu 21.5.20, Magisk v23)

I don't know what's wrong now - I tried to repeat everything with Xiaoni eu 21.6.9:
- Connected again my phone to (the same PC), ran SnaliPatcher (as admin) again, successfully created a module for Secure Screenshot
- Module installls from Magisk app with no errors (everyrthing the same as when did first time for 21.5.20)
But when I reboot, it fails and after a long time staying on MIUI splash screen, it eventually reboots to TWRP.
I have to remove the module to be able to boot
Tried two times (rebuilding the module by SmaliPatcher, installing the new module), no success

zgfg said:
I don't know what's wrong now - I tried to repeat everything with Xiaoni eu 21.6.9:
- Connected again my phone to (the same PC), ran SnaliPatcher (as admin) again, successfully created a module for Secure Screenshot
- Module installls from Magisk app with no errors (everyrthing the same as when did first time for 21.5.20)
But when I reboot, it fails and after a long time staying on MIUI splash screen, it eventually reboots to TWRP.
I have to remove the module to be able to boot
Tried two times (rebuilding the module by SmaliPatcher, installing the new module), no success
Click to expand...
Click to collapse
Managed to make the module again with Xiaomi.eu 21.6.16:
- I used SmaliPatcher to create the module before (!!!) I installed Magisk.
That is, I installed Xiaomi.eu 21.6.16 and used SmaliPatcher to create the module for Secure Screenshot, only then I installed Magisk and finally installed my SmaliPatcher module - it boots properly to Magisk and Secure Printing works
I think this is the same way I also successfully used SmaliPatcher with Xiaomi.eu 21.5.20
However, when I was on Xiaomi.eu 21.6.9 and when I reported a bootloop, I did it by slightly different order:
- I upgraded to 21.6.9 and immediately installed Magisk, then I used SmaliPatcher to create the module, installed the module and rebooted, but instead of to system it eventually booted to Recovery (TWRP)

This is actually what I was looking for. Btw some apps don't allow us to copy / paste, could you help me with this problem?

verydp1 said:
This is actually what I was looking for. Btw some apps don't allow us to copy / paste, could you help me with this problem?
Click to expand...
Click to collapse
Settings, Apps, find your app, Permissions and enable Access items in the clipboard

this give me a bootloop, anyone know other apps that can do Secured ScreenShot

remorze said:
this give me a bootloop, anyone know other apps that can do Secured ScreenShot
Click to expand...
Click to collapse
Magisk module as attached to OP post will work for you only if you have Mi 9T Pro/Redmi K20 Pro with Xiaomi.eu 21.5.20 (exactly that build)
Otherwise you have to install SmaliPatcher to PC, connect to your phone and follow instructions for the patcher to make yourself the Magisk module for your phone
I don't have Pro but 'plain' Mi 9T, and I'm on newer Xiaomi.eu builds, hence I had to do myself Magisk modules three times (Xiaomi.eu weekly releases).
First time it worked fine for me, next time I also had the bootloop when I made and installed the module (AFAIK, I was following the same patching procedure, with the same phone and PC, hence I don't understand why that time I had a problem). Third time again everything was ok (I got the module for Magisk that does not produce bootloop and it 'unlocks' screenshoting from the apps otherwise not allowing)

Related

[Magisk][Module]HTC 10 SafetyNET fix for any ROM

Hello everyone !
As you know this module help you to fix Safetynet by change build fingerprint to Xiaomi Mi 6s
But when you use the original module, Google will show your device as Xiaomi Mi 6s
I made a little modify to change build fingerprint to our HTC stock ROM, it'll show your device as HTC 10
A build will release when the original build release, same time !
Some report said that you can use this module for HTC stock ROM, I can't help you if you got error about this ROM
Download : Move to Download tab
ROM tested : LineageOS (official), RR (official)
This required :
No Xposed and SuperSU, even systemless
Systemless modifications in your system only
MagiskSU
Magisk Hide working properly
Main thread : https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Thanks to : @Deic for his source code
XDA:DevDB Information
HTC 10 (pme) SafetyNET fix, Tool/Utility for the HTC 10
Contributors
hiimpig1
Source Code: https://github.com/piiiggg/xiaomi-safetynet-fix/tree/pme
Version Information
Status: Stable
Created 2017-06-25
Last Updated 2017-06-28
Update some screenshot
Tested on : LOS official and RR official ROMs
Can confirm that this work on stock ROM, if any magisk module cause safetynet to fail. Thanks for your work!
azZA_09 said:
Can confirm that this work on stock ROM, if any magisk module cause safetynet to fail. Thanks for your work!
Click to expand...
Click to collapse
Thanks, I'll note it on #1
Installing it made my mobile data not turn on anymore, as well as killing off wifi, and magisk. it also unrooted me. it basically ruined my phone. wow.
tiki2134 said:
Installing it made my mobile data not turn on anymore, as well as killing off wifi, and magisk. it also unrooted me. it basically ruined my phone. wow.
Click to expand...
Click to collapse
I think you have to enable force encrypt when install magisk, try this
Install any kind of root like supersu - download magisk manager - install magisk without disable force encrypt - uninstall supersu - install module
I never use stock rom so idk, I only tested on custom ROM
tiki2134 said:
Installing it made my mobile data not turn on anymore, as well as killing off wifi, and magisk. it also unrooted me. it basically ruined my phone. wow.
Click to expand...
Click to collapse
Same thing happened to mine. Get the uninstall zip from the Deic thread referenced above and it will put your phone back where it was. You'll have to download it to your computer first and then copy it to your SD card via USB or putting your card into your computer. Then get into the recovery by powering down and holding the power and vol-down keys to get into Boot loader or using the power key options in your ROM, if present. I couldn't get into the Recovery with the power key options but could get into the Boot loader. Once in the Boot loader, use the volume-down key to get to the recovery option and execute it by pushing the power key. From recovery install the uninstall that you copied to your SD card (internal or external) and reboot. My phone came back up in the same state as before trying the module.
lichan said:
Same thing happened to mine. Get the uninstall zip from the Deic thread referenced above and it will put your phone back where it was. You'll have to download it to your computer first and then copy it to your SD card via USB or putting your card into your computer. Then get into the recovery by powering down and holding the power and vol-down keys to get into Boot loader or using the power key options in your ROM, if present. I couldn't get into the Recovery with the power key options but could get into the Boot loader. Once in the Boot loader, use the volume-down key to get to the recovery option and execute it by pushing the power key. From recovery install the uninstall that you copied to your SD card (internal or external) and reboot. My phone came back up in the same state as before trying the module.
Click to expand...
Click to collapse
The module change (faking) bootloader unlock status, could be a problem with HTC stock ROM. When you got this problem, after install Magisk or install my module ?
hiimpig1 said:
The module change (faking) bootloader unlock status, could be a problem with HTC stock ROM. When you got this problem, after install Magisk or install my module ?
Click to expand...
Click to collapse
This was on an HTC 10 with Viper 10 ROM with Magisk 12 and Magisk SU installed with Magisk Hide activated. It happened after installing the Safety Net fix. I did not have Magisk encryption enabled and may have had a couple of modules installed. I may try some different things to see if I can get it to work later.
lichan said:
This was on an HTC 10 with Viper 10 ROM with Magisk 12 and Magisk SU installed with Magisk Hide activated. It happened after installing the Safety Net fix. I did not have Magisk encryption enabled and may have had a couple of modules installed. I may try some different things to see if I can get it to work later.
Click to expand...
Click to collapse
Radio not working on stock ROM because encryption not enable, a guy was taking about this before. Or changing stock ROM bootloader status could cause this problem.
It was working fine earlier, but now I updated to 13.2 & safety check stopped working, uninstalled from Tarp uninstaller & reinstalled the 12.0, flashed safety check for HTC 10, but safety check fails please tell me how to fix
aryan_rulz_1983 said:
It was working fine earlier, but now I updated to 13.2 & safety check stopped working, uninstalled from Tarp uninstaller & reinstalled the 12.0, flashed safety check for HTC 10, but safety check fails please tell me how to fix
Click to expand...
Click to collapse
Sorry, I was sold my device. You can learn how to make new version of this module on main thread
aryan_rulz_1983 said:
It was working fine earlier, but now I updated to 13.2 & safety check stopped working, uninstalled from Tarp uninstaller & reinstalled the 12.0, flashed safety check for HTC 10, but safety check fails please tell me how to fix
Click to expand...
Click to collapse
The 13.3 update was released last night, thos should fix.

magisk + xposed problem

Hi all,
I have installed Magisk 16.0 based on Maik93's post, and Xposed Framework SDK27 90.2-beta3 (Systemless), through Magisk modules.
When I enable the Xposed module, the phone first shows endless boot animation, and when restarting it again, it boots, but the Xposed app seems not installed (not listed in Settings->Apps and its icon is not present in chooser), although, in Magisk, it is visible in the Modules and it's checkbox is checked.
Did anybody successfully installed Xposed with A2 Lite? What can be the problem?
Thanks a lot,
Circum
Did you install the apk of xposed?
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
https://forum.xda-developers.com/attachment.php?attachmentid=4393082&d=1516301692
Here is the link from xda
No, sorry, I was not aware that it is a separate thing.
Now I have installed, but it says that no Xposed Framework is installed. If I try to install a framework from inside the installer (90-beta3), it -- obviously -- reports an error that /system/framework/XposedBridge.jar already exist...
Because of this, I cannot enable any module from Xposed Installer.
Any tips what do I do wrong?
I want to use Xposed too but we will have to wait for TWRP I guess.
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
mik.y said:
I want to use Xposed too but we will have to wait for TWRP I guess.
Click to expand...
Click to collapse
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
HoangP05 said:
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
Click to expand...
Click to collapse
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
mik.y said:
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
Click to expand...
Click to collapse
Not all are working apparently, but if it is bootloop, you so try to let it boot again, press power and volume down as the same time while it bootloop, the second boot always work for me
There is TWRP for Mi A2 Lite.
Search on google.
NOTICE: For now there isn't official TWRP. There'w unofficiak fork which can you install using fastboot. :good:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
HoangP05 said:
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
Click to expand...
Click to collapse
Xposed's Gravity box module works on Mi A2 lite?
Yes, GravityBox is working, although as I mentioned, there are issues with boot - I have to reboot several times until it succeeds...
performace drops significantly when i install the xposed module for magisk. i hope they fix it.
So far everything works fine on my end, I'm not noticing any performance drops in my day to day use. Then again I haven't used it much without Magisk + exposed but from what i'm seeing it's working well, no noticeable lag or stuttering.
I have gravity box, Amplify and Greenify modules running.
circum said:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
Click to expand...
Click to collapse
Magisk alone didnt give me boot problems. What rooting guide did you follow?
fake__knv said:
Magisk alone didnt give me boot problems. What rooting guide did you follow?
Click to expand...
Click to collapse
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
circum said:
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
Click to expand...
Click to collapse
I can assure you @BubuXP's guide is good. Used his rooting guide, followed the steps for updates and its good to go. I rooted my phone when Im on August update. Now Im in September update

[GSI][UNOFFICIAL] LineageOS 17.1 Modified [TEST][XT1952-2]

MODIFIED EXCLUSIVELY FOR MOTO G7 PLAY
WARNING
Do not try to install this via fastboot, remove the magisk, to remove just reinstall the Stock Rom
MAIN FEATURES
Root modified by Spaceminer
More speed
Added multiple apps
Several useless apps removed
Black theme automatically enabled in all supported applications
Gapps already installed
Notch fix
And more
DOES NOT WORK
Fingerprint
Automatic brightness
INSTALLATION INSTRUCTION
1. Download and extract
2. Put the GSI on your memory card
3. Restart your phone in Bootloader / Fastboot mode
4. Open fastboot on your computer
use the command: fastboot -w
use the command: fastboot boot twrp.img
5. TWRP: Install> Install image> Choose image file> Flash on the system
DOWNLOADS
TWRP by Spaceminer: https://mega.nz/#!roRzBCTK!THHq0VMWqgtowJNkY-Id3b9S9H9dhzsJhE83k0Kvt2k
GSI: https://www.drive.google.com/file/d/1000HaJJqMdGyOtEd7ribp4n5Eb9l-3my/view
Works great apart from when I make calls the microphone doesn't work...whatsapp calls are fine it only seems to be a problem on cellular!
When I select the image I get 4 options and it does not let me install with any
With this my G7 play stay 32bits or can change for 64 bits?
RafaelItape said:
With this my G7 play stay 32bits or can change for 64 bits?
Click to expand...
Click to collapse
until we get a 64 bit kernel, it'll stay 32. i want to build a 64 kernel cause i want to bring ubuntu touch to this phone, that requires a 64 bit boot image, if we are to use erfan's (only method for android 9 devices rn)
Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone
CFKod said:
Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone
Click to expand...
Click to collapse
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting
BobbyBlunt said:
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting
Click to expand...
Click to collapse
yup... sorry, forgot to post... I assumed it was after installing modules.
Lockscreen not work for me, in all gsi roms.
Only stock works.
rom works great, feels like a new phone.
model XT1952-4.
not working unfortunately is the FM radio.
based on the error message when trying to install FM apps, it looks like the kernel driver was not included in the rom?
I can deal with the fingerprint not working, it would be really nice to get the FM driver included so I don't have to use data.
Overall the phone is so much better with this rom, Thank You!!!!
Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)
Thanks for all the work
Everything seems stable been using on daily driver for 2 days now. Only issue is bluetooth audio not working. I'm wondering if the Motorola face unlock app would work however current version isn't available.
gadolf said:
Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)
Click to expand...
Click to collapse
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.
XxLilJeepXx said:
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.
Click to expand...
Click to collapse
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17
Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage
workin on fixing phone
yashor said:
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17
Click to expand...
Click to collapse
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.
XxLilJeepXx said:
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.
Click to expand...
Click to collapse
Why not just boot into bootloader mode and fast boot stock firmware to recover your device ?
PoochyX said:
Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage
Click to expand...
Click to collapse
Hi,
From your experience which GSI is better for MOTO G7 Play 1952-2:
Havoc or Lineage ?
It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...
PoochyX said:
It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...
Click to expand...
Click to collapse
Thank you for your reply.
I favor stability and performance over Magisk.
In my case, do your recommend Lineage as my best option to try?

Question Interested in a Working Formula to get Viper4Android Working? (ROOT)

Viper4Android for Google Pixel 6/6 Pro and most other devices on Android 12...
It the time of testing this Method, it worked in November 2021 and December 2021 builds for my Google Pixel 6....
1) Make sure your BL is unlocked and you are ROOTed via Magisk.
2) 1st I installed the attached Viper4Android file WITHOUT opening it.
3) The 2nd file Which is the FIX for Android 12. That can be flashes via Magisk BUT DONOT REBOOT.
4) Once you have installed apk and flash FIX.zip via Magisk, now Grant Magisk SU Rights, Install Driver's, let it automatically reboot.
5). Viper ~~>Settings~~> Legacy Mode Flipped On
6) Enjoy
*Edit*
ADDED Status Screenshot
that's just copying the same post-fs-data.sh file we've been using since like 2019
Roll3r said:
that's just copying the same post-fs-data.sh file we've been using since like 2019
Click to expand...
Click to collapse
And is stolen from here, without any credit
Typhus_ said:
Hello!
I've got Viper4Android version 2.7.2.1 working on Android 12 without the need for any other module installed and with SELinux enforcing.
I've found another thread where other users where talking about Viper on Android 12 and saw THIS post by @TheExoduser.
That solution, in fact, works, so I came up with a simple Magisk module that just changes the script.
All that this "fix module", attached bellow, does is to update the post-fs-data.sh script, included on official installer by @Team_DeWitt and deletes itself after replacing the script.
This is done after 20 seconds upon the reboot, we have to do on Magisk, after installing the fix.
As soon as the script is changed and the fix gets deleted by itself, you may need to enable Legacy mode, on Viper4Android app, choose your desired options and reboot the device again.
If you don't reboot again you won't notice any audio change.
Sometimes a second reboot is needed (faced that during my tests).
Hope this helps.
Cheers!
Click to expand...
Click to collapse
No problem. As long as it helps other users I don't mind that anyone shares it to the world. Credits would be nice though but... whatever...
Merry Christmas to everyone.
Cheers!
DanielF50 said:
And is stolen from here, without any credit
Click to expand...
Click to collapse
Stolen fair and square yo!

[OOS13] IN2023_11_F.13 Patched boot.img

Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
fastboot flash boot IN2023_11_F13-Patched.img
Click to expand...
Click to collapse
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive
Thanks for this. Where can you download the oos13 firmware?
MR0808 said:
Thanks for this. Where can you download the oos13 firmware?
Click to expand...
Click to collapse
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features
Thanks. Looks like I'm getting IN2025, so will have to do the patched boot.img myself.
Time to find my old notes somewhere
Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF
GhostRider86 said:
Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF
Click to expand...
Click to collapse
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know
Neil_Armstrong_ said:
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know
Click to expand...
Click to collapse
I keepted mine as well, SafetyNet and gPay are working, but Unlock with Fingerprint Sensor is not. No reaction to sensor at all, not able to register new Finger...
Edit: Working now. Needed to disable USNF module, no reboot, Fingerprint Sensor working, register Fingers, screen lock, test, enable USNF module, enjoy
Neil_Armstrong_ said:
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features
Click to expand...
Click to collapse
I already have the fil, but I can't install it from system update apk,
am I missing something ?
EDIT:
re-downloaded the file again from Oxygen updater, but still it fails to install nd also "verification failed" in system local update.
Edit 2:
I re MSM back to OOS11 and upgraded directly to OOS 13 F3.
Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works
Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help
VBBoston said:
Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help
Click to expand...
Click to collapse
I updated from oos 13 unrooted. Lost my root using oos12
I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~
VBBoston said:
I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~
Click to expand...
Click to collapse
They have already been shared here.
Thank you very much!
stell52 said:
Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works
Click to expand...
Click to collapse
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated
Neil_Armstrong_ said:
Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive
Click to expand...
Click to collapse
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks
MrBloB said:
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated
Click to expand...
Click to collapse
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know
MrBloB said:
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks
Click to expand...
Click to collapse
Flash Universal SafetyNet module in magisk (kdrag0n) and Magisk Bootloop Protector (just in case)
Check your status after a reboot with YASNAC from Play Store
Force the Magisk DenyList, and when configuring it, develop the apps and check all the tick boxes manually (to be sure)
Uninstall Netflix and install the latest .apk from APKMirror, can't help as other app (banking too) works fine
Isn't vanced dead ?
YouTube Premium Argentina is very affordable fyi ....
stell52 said:
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know
Click to expand...
Click to collapse
stell52 said:
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
Click to expand...
Click to collapse
Yes i have done this. Tried shamiko as well. M passing safetynet checks, still it doesnt work.

Categories

Resources