Develop Bugs

(Qualcomm) F2FS patched stock kernel for fully working Magisk

https://forum.xda-developers.com/showpost.php?p=74962276&postcount=9
Merry Christmas everyone! Check out the following post for installation instructions.?

GetOffMyLawn&!+¢#{$ said:
https://forum.xda-developers.com/showpost.php?p=74962276&postcount=9
Merry Christmas everyone! Check out the following post for installation instructions.?
Click to expand...
Click to collapse
Thanks for asking him to build, that was awesome bro.

madbat99 said:
Thanks for asking him to build, that was awesome bro.
Click to expand...
Click to collapse
Np. Wasn't expecting it to happen so fast. I was going to do it myself after Christmas, but... Looks like we finally got a good mind around here.
Sent from my Moto E (4) Plus using XDA Labs

In case anyone is interested, here is an explanation of the bug, and the patch: https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
Sent from my Moto E (4) Plus using XDA Labs

GetOffMyLawn&!+¢#{$ said:
Np. Wasn't expecting it to happen so fast. I was going to do it myself after Christmas, but... Looks like we finally got a good mind around here.
Click to expand...
Click to collapse
I was going to attempt it as well. His worked fine for me. I patched his boot.img with magisk and installed it in twrp (install image to boot). After backing up boot of course.
I only describe the steps because someone will inevitably try without backing up or something and come back asking for help recovering, lol.

madbat99 said:
I was going to attempt it as well. His worked fine for me. I patched his boot.img with magisk and installed it in twrp (install image to boot). After backing up boot of course.
I only describe the steps because someone will inevitably try without backing up or something and come back asking for help recovering, lol.
Click to expand...
Click to collapse
I just flashed the kernel with TWRP and then Magisk. Worked just fine.
Sent from my Moto E (4) Plus using XDA Labs

GetOffMyLawn&!+¢#{$ said:
I just flashed the kernel with TWRP and then Magisk. Worked just fine.
Click to expand...
Click to collapse
Cool, same thing. Flash kernel then magisk =patched boot.img
Patch image with magisk = patched boot.img. I already had magisk installed and kinda wanted to try the "patch boot.img method in magisk anyways.
Thanks again dude, I was missing modules for awhile there. You had any luck with safetynet?

madbat99 said:
Cool, same thing. Flash kernel then magisk =patched boot.img
Patch image with magisk = patched boot.img. I already had magisk installed and kinda wanted to try the "patch boot.img method in magisk anyways.
Thanks again dude, I was missing modules for awhile there. You had any luck with safetynet?
Click to expand...
Click to collapse
No
Sent from my Moto E (4) Plus using XDA Labs

GetOffMyLawn&!+¢#{$ said:
No
Click to expand...
Click to collapse
Using systemless Xposed. Switched it off, cleared data for play store, bam passed safetynet. Never could get it, even without Xposed before

madbat99 said:
Using systemless Xposed. Switched it off, cleared data for play store, bam passed safetynet. Never could get it, even without Xposed before
Click to expand...
Click to collapse
Systemless Xposed wouldn't work on my E4 Plus when I tried. It said it wasn't active. I'll have to try again.
Sent from my Moto E (4) Plus using XDA Labs

GetOffMyLawn&!+¢#{$ said:
Systemless Xposed wouldn't work on my E4 Plus when I tried. It said it wasn't active. I'll have to try again.
Click to expand...
Click to collapse
I just used the one in the magisk repo. Gotta use his Xposed installer APK too

madbat99 said:
I just used the one in the magisk repo. Gotta use his Xposed installer APK too
Click to expand...
Click to collapse
That is what I tried.
Sent from my Moto E (4) Plus using XDA Labs

Will SuperSU work now with this fixed kernel??

PimpMy5Ton said:
Will SuperSU work now with this fixed kernel??
Click to expand...
Click to collapse
Yes, in fact, the original post detailing how to patch this was on the SuperSU thread.

Check this out everyone:
Sent from my Moto E (4) Plus using XDA Labs

madbat99 said:
Using systemless Xposed. Switched it off, cleared data for play store, bam passed safetynet. Never could get it, even without Xposed before
Click to expand...
Click to collapse
If I'm on 7.1.2 does that have a effect on whether the Kernel will flash sucesfully?

INF3XPL0IT said:
If I'm on 7.1.2 does that have a effect on whether the Kernel will flash sucesfully?
Click to expand...
Click to collapse
This phone doesn't have stock 7.1.2
This is a kernel for stock, not custom roms.

Certified play store and pass safetynet

Hello guys,
I decided to make this post as I saw a lot of questions about this and as well a zip flashed to make safetynet pass on custom roms.
Well with this one, you will have play store certified as well as pass safetynet and will get no annoying message at the phone starting.
What we will do is change our fingerprint to a certified one. So here it is:
1. You need to be rooted with magisk.
2. You need to have any terminal emulator, you can download any on the play store.
3. Go to downloads on magisk and download the module: "Magiskhide props config", install and reboot.
4. After you had your device rebooted, open terminal emulator and type:
Su
Allow super user.
5. Now type:
Props
A list of options will appear. What we need from the module is choose a certified fingerprint. So we will choose option 1.
After option 1, you need to choose the option with letter "f" which is pick a certified fingerprint.
Then we will have a list of brands, we need to, of course, choose Xiaomi, option 11.
After we pick xiaomi, we need to pick our device, which is vince, XRN5/ XR5P option 16.
Then it will as us twice if we are sure, we type letter "y" twice to confirm and reboot
After rebooting you can see safetynet ctsprofile:true and play store certified.
I have tried in almost all roms around here including the miui ones and always worked flawlessly, hopefully it helps you also.
Any questions, post it here. Remember that you need to press enter after picking any choice.
Credits: @Didgeridoohan creator of the module

I'm using Havoc OS (8.1) and whenever I try to check the safenety pass, the magisk closes.

Can you make a tutorial for custom rom like pixel experience?

Is working man thanks I'm rr rom

Allhunt said:
I'm using Havoc OS (8.1) and whenever I try to check the safenety pass, the magisk closes.
Click to expand...
Click to collapse
Are you using latest magisk manager version? I am on that rom also, magisk 5.8.1. Working fine here.
clintandrewph said:
Can you make a tutorial for custom rom like pixel experience?
Click to expand...
Click to collapse
This is the tutorial bro, it is made for all custom AOSP and MIUI Roms, it should work with no issues.
luisrosales0130 said:
Is working man thanks I'm rr rom
Click to expand...
Click to collapse
You're welcome man. Glad to help.

Dunno why i got Bluetooth issues after install I'm using resurrection remix 8.1.0 is something relating this module?

luisrosales0130 said:
Dunno why i got Bluetooth issues after install I'm using resurrection remix 8.1.0 is something relating this module?
Click to expand...
Click to collapse
Nope, I have my Bluetooth controller connected with no issues whatsoever. This just makes a change in build.prop that has nothing to do with wireless radios.

Tried this but didn't work.... I'm on RR rom latest build...
Please help

Shree26 said:
Tried this but didn't work.... I'm on RR rom latest build...
Please help
Click to expand...
Click to collapse
If you give me more info maybe I can help. Can you give me screenshots of the module being active and the props changed on the terminal emulator?

Jemec26 said:
If you give me more info maybe I can help. Can you give me screenshots of the module being active and the props changed on the terminal emulator?
Click to expand...
Click to collapse
Did all the steps and rebooted the phone.
Still ctsprofile is false

Shree26 said:
Did all the steps and rebooted the phone.
Still ctsprofile is false
Click to expand...
Click to collapse
And the screenshots?

Jemec26 said:
And the screenshots?
Click to expand...
Click to collapse
Here u go..

Shree26 said:
Here u go..
Click to expand...
Click to collapse
if you not using xposed, voenabler module can be the culprit...

Shree26 said:
Here u go..
Click to expand...
Click to collapse
Thanks, I tested this on Vince . Did not know you were using whyred. In that case, I can't really tell you what happens there.

Even though fingerprinting with nougat rom is ok, is there any oreo working fingerprint that passes cts?
Question: didnt nougat fingerprint interfere when flashing other general files which checks the android version before flashing?

Reykawick said:
Even though fingerprinting with nougat rom is ok, is there any oreo working fingerprint that passes cts?
Question: didnt nougat fingerprint interfere when flashing other general files which checks the android version before flashing?
Click to expand...
Click to collapse
1. There will not be until Miui 10 with 8.1 Oreo stable version is released. Then I guess module creator will update the fingerprint as it will be certified.
2. No. It does not interfere.

I have a question: I don't like to have my phone rooted. If after following your guide I remove root, will it work?
Thanks.

Samuele Ribaudo said:
I have a question: I don't like to have my phone rooted. If after following your guide I remove root, will it work?
Thanks.
Click to expand...
Click to collapse
Well, if you remove root, module will be deactivated. So it won't work then.

on Pie (with root\magisk).. anyone have a trick for increasing volume steps

It seems as though comfortable listening for me is directly between two of the current steps, which have a massive jump in db tiny ears.
Thus, I'm looking for something that increases the volume steps from 15 to 30+.
Have found a few magisk modules that are outdated and\or don't work on Pie. Anyone have another solution, or will I need to edit build.prop as described elsewhere?

I'm using here's 14.0.0.zip on my Pixel2 with Pie and magisk 16.7 flawless,
https://forum.xda-developers.com/apps/magisk/module-volume-steps-increase-magisk-v10-t3554996
and here is unofficial updated version (I have not tried yet),
https://forum.xda-developers.com/showpost.php?p=77033982&postcount=75

moviti said:
I'm using here's 14.0.0.zip on my Pixel2 with Pie and magisk 16.7 flawless,
https://forum.xda-developers.com/apps/magisk/module-volume-steps-increase-magisk-v10-t3554996
and here is unofficial updated version (I have not tried yet),
https://forum.xda-developers.com/showpost.php?p=77033982&postcount=75
Click to expand...
Click to collapse
This is what I get

jewnersey said:
This is what I get
Click to expand...
Click to collapse
Have you tried to install it via TWRP?

moviti said:
Have you tried to install it via TWRP?
Click to expand...
Click to collapse
Same error

jewnersey said:
Same error
Click to expand...
Click to collapse
Use the unofficial one provided. The original's Magisk template isn't updated.

Ariac Konrel said:
Use the unofficial one provided. The original's Magisk template isn't updated.
Click to expand...
Click to collapse
Excellent thanks

Gravity Box + EdXposed

Has anyone been successful in getting it to work on this this device?
I'm on at XT1922-5 retbr Running Pie.

Kuntitled said:
Has anyone been successful in getting it to work on this this device?
I'm on at XT1922-5 retbr Running Pie.
Click to expand...
Click to collapse
Yes on XT1922-7

damprobot said:
Yes on XT1922-7
Click to expand...
Click to collapse
I unfortunately couldn't. I get edXposed to install fine, even used some modules with no problems. But GB just refuses to work.

Kuntitled said:
I unfortunately couldn't. I get edXposed to install fine, even used some modules with no problems. But GB just refuses to work.
Click to expand...
Click to collapse
Use latest gravitybox edxposed edition

damprobot said:
Yes on XT1922-7
Click to expand...
Click to collapse
damprobot said:
Use latest gravitybox edxposed edition
Click to expand...
Click to collapse
I believe i have. I tried the beta-7 version of Gravity Box

Kuntitled said:
I believe i have. I tried the beta-7 version of Gravity Box
Click to expand...
Click to collapse
I'm such a genius. I realized I was using the gravity box pie beta. Don't forget to thank @C3C076!
https://forum.xda-developers.com/xposed/modules/app-gravitybox-v9-0-0-beta-1-android-9-t3908768

damprobot said:
I'm such a genius. I realized I was using the gravity box pie beta. Don't forget to thank @C3C076!
https://forum.xda-developers.com/xposed/modules/app-gravitybox-v9-0-0-beta-1-android-9-t3908768
Click to expand...
Click to collapse
Still doesn't work for me. I have no idea why.

Kuntitled said:
Still doesn't work for me. I have no idea why.
Click to expand...
Click to collapse
That's weird. I'm on aosp pie gsi and it works perfectly. What I did:
1. Flash latest riru core zip via magisk
2. Flash latest edexposed framework zip via magisk
3. Reboot
4. Install latest edexposed app
5. Install and enable latest gravitybox pie beta apk
6. Reboot and try tweaks!
That's all there is to it

Viper on Q

Anyone been able to get v4A working on Q?
Android Q, latest update, Pixel 3XL, app installs, but driver doesn't install. Magisk repo, classic v4a caused booting issues, driver doesn't install.
AML installed.
Rooted with Magisk 19.4 beta
Sent from my Pixel 3 XL using Tapatalk

MeetFace said:
Anyone been able to get v4A working on Q?
Android Q, latest update, Pixel 3XL, app installs, but driver doesn't install. Magisk repo, classic v4a caused booting issues, driver doesn't install.
AML installed.
Rooted with Magisk 19.4 beta
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Are you using the latest V4A? The one from the link below works. You'll have to let it install the driver and reboot a few times before it takes. I can confirm it works great.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

Yeah, installed and rebooted twice. Perhaps I'll try again and try it 4 times
Sent from my Pixel 3 XL using Tapatalk

Still no luck. Which Magisk are you using?
Sent from my Pixel 3 XL using Tapatalk

Screen shot of it working on Q anyone? Otherwise I call shanaigans!
Sent from my Pixel 3 XL using Tapatalk

MArtyChubbs said:
Screen shot of it working on Q anyone? Otherwise I call shanaigans!
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
If you are that obsessed with proof, I can provide you with that. Instead, how about reading the thread below. It was not the simplest install (newest XDA labs download and these instructions https://www.jpoirier.net/index.php/2019/09/12/how-to-install-viper4android-on-android-10/), but it definitely works.
https://forum.xda-developers.com/pixel-3-xl/how-to/helpful-tip-viper4android-t3981803
Edit - Here's the screenshot.

just tried and i get stuck at installing the viper driver the first time. it says it doesn't have root access and i do not get prompted to grant access. magisk looks like it gets hung on root access while it is waiting to reboot after installing audio modification library.

Go into superuser and make sure it is not disabled.
Also, you might have to be on Canary Magisk. I had issues until switching to Canary, non stable
Sent from my Pixel 3 XL using Tapatalk

sliding_billy said:
If you are that obsessed with proof, I can provide you with that. Instead, how about reading the thread below. It was not the simplest install (newest XDA labs download and these instructions https://www.jpoirier.net/index.php/2019/09/12/how-to-install-viper4android-on-android-10/), but it definitely works.
https://forum.xda-developers.com/pixel-3-xl/how-to/helpful-tip-viper4android-t3981803
Edit - Here's the screenshot.
Click to expand...
Click to collapse
I've followed those instructions and always get abnormal driver however your screenshots show that it is possible thanks for sharing
Sent from my Pixel 3 XL using Tapatalk

MArtyChubbs said:
I've followed those instructions and always get abnormal driver however your screenshots show that it is possible thanks for sharing
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Somewhere in the other instructions it mentioned removing all audio mods before installing V4A. It didn't impact me, but I believe that was the issue for another user.