Related
Anyone here using Magisk with no issues in EMUI 5.1?
adriansticoid said:
Anyone here using Magisk with no issues in EMUI 5.1?
Click to expand...
Click to collapse
Not all devices are updated to emui 5.1 mate. Hoping someone can help. Venu had it working but on Honor 8 with emui 5.0 (i think, i saw his one of post, it was for FRD model)
shashank1320 said:
Not all devices are updated to emui 5.1 mate. Hoping someone can help. Venu had it working but on Honor 8 with emui 5.0 (i think, i saw his one of post, it was for FRD model)
Click to expand...
Click to collapse
I had it working before also in Honor 8 B385. OldDroid was saying something about flashing a file that would keep the device from being encrypted at boot. But I can't find it anywhere.
Sent from my DUK-L09 using XDA Labs
adriansticoid said:
I had it working before also in Honor 8 B385. OldDroid was saying something about flashing a file that would keep the device from being encrypted at boot. But I can't find it anywhere.
Click to expand...
Click to collapse
No idea mate. Yet to try magisk
shashank1320 said:
No idea mate. Yet to try magisk
Click to expand...
Click to collapse
That's ok mate. I don't want any other root solution other than Magisk. So I hope it settles soon.
Sent from my DUK-L09 using XDA Labs
Rooted with Magisk today and works seamless.
But I could not pass SafetyNet check.
First time I flashed a zip to remove dm-verity and it ran into bootloop. Make sure you don't do that
amulbaby said:
Rooted with Magisk today and works seamless.
But I could not pass SafetyNet check.
First time I flashed a zip to remove dm-verity and it ran into bootloop. Make sure you don't do that
Click to expand...
Click to collapse
Thabjs for warning and preventing others from bootloop
Could someone running from a stock kdz post their ro.build.fingerprint and ro.build.description values?
Thanks
obvious said:
Could someone running from a stock kdz post their ro.build.fingerprint and ro.build.description values?
Thanks
Click to expand...
Click to collapse
I have cts false too in Magisk 14th and 29a...
Yeah, it may be possible to fool safetynet into thinking we have a different CTS certified Rom just by tinkering with ro.build.fingerprint
Might let android pay run on V29a
Safetynet works lol. I use android pay and all that just download safetynet fix
What's your setup?
I'm on Freedom rom, Titan kernel and magisk 14 or 13.3 with or without fix. Banking app works but not android pay
H815 international in the UK
obvious said:
What's your setup?
I'm on Freedom rom, Titan kernel and magisk 14 or 13.3 with or without fix. Banking app works but not android pay
H815 international in the UK
Click to expand...
Click to collapse
Have you disabled logging? Because that trips SafetyNet
da.vandenham said:
Have you disabled logging? Because that trips SafetyNet
Click to expand...
Click to collapse
Good thought but it's not that. Lolcat still showing usual activity
obvious said:
Good thought but it's not that. Lolcat still showing usual activity
Click to expand...
Click to collapse
The only way I got Freedom to pass SafetyNet was by installing it and leaving every option as close to stock as possible, installing Magisk and the Universal SafetyNet Fix module. Also, don't make any modification to the system partition
da.vandenham said:
The only way I got Freedom to pass SafetyNet was by installing it and leaving every option as close to stock as possible, installing Magisk and the Universal SafetyNet Fix module. Also, don't make any modification to the system partition
Click to expand...
Click to collapse
Well that's what I've done too. So your CTS profile passes? Are you able to use android pay or at least launch without error?
Are you running Titan kernel?
obvious said:
Well that's what I've done too. So your CTS profile passes? Are you able to use android pay or at least launch without error?
Are you running Titan kernel?
Click to expand...
Click to collapse
I'm currently testing a MM rom which I modded myself, but to answer your question: yeah it passed with Titan Kernel. All V29A roms I tried did.
Edit:
Never tried Pay, I live in The Netherlands so never had a use for it
obvious said:
What's your setup?
I'm on Freedom rom, Titan kernel and magisk 14 or 13.3 with or without fix. Banking app works but not android pay
H815 international in the UK
Click to expand...
Click to collapse
Sorry for long reply. Next time mention me just flash safetynet fix from magisk downloads
Sent from my LGE V30 using XDA Labs
Minto107 said:
Sorry for long reply. Next time mention me just flash safetynet fix from magisk downloads
Sent from my LGE V30 using XDA Labs
Click to expand...
Click to collapse
No prob. Like I said though...
What's your setup?
I'm on Freedom rom, Titan kernel and magisk 14 or 13.3 with or without fix. Banking app works but not android pay
Click to expand...
Click to collapse
obvious said:
No prob. Like I said though...
Click to expand...
Click to collapse
I guess you modified your /system then
Sent from Galaxy Tab A10 with 7300 battery ))
Minto107 said:
I guess you modified your /system then
Click to expand...
Click to collapse
That's what it looks like. Not sure how though.
Is there something super secret about your working setup?
I've asked you about 4 times, in bold and everything lol
obvious said:
That's what it looks like. Not sure how though.
Is there something super secret about your working setup?
I've asked you about 4 times, in bold and everything lol
Click to expand...
Click to collapse
Clean V30 magisk 14 titan kernel fix and few others module. Does it show 2 red crosses? If so module won't work
Sent from Galaxy Tab A10 with 7300 battery ))
Minto107 said:
Clean V30 magisk 14 titan kernel fix and few others module. Does it show 2 red crosses? If so module won't work
Sent from Galaxy Tab A10 with 7300 battery ))
Click to expand...
Click to collapse
Hmm, v30.
obvious said:
Hmm, v30.
Click to expand...
Click to collapse
I had same and universal safetynet fix worked just fine. Maybe we're talking about different fixes?
Sent from Galaxy Tab A10 with 7300 battery ))
I had the same profile error on my v29a. Is it possible to fix it with any of the proposed solutions ( universal fix or safetynet patch) and still be able to relock Bootloader ?
Sambu_k said:
I had the same profile error on my v29a. Is it possible to fix it with any of the proposed solutions ( universal fix or safetynet patch) and still be able to relock Bootloader ?
Click to expand...
Click to collapse
You can relock bootloader and it shouldn't be an issues then
Sent from my LGE V30 using XDA Labs
Good day, I have a little problem with my 5x, when I long click on the power button, the power menu doesn't appear. Instead, I go to the boot animation and it just restarts, without showing the Google's logo.
Note that I use LineageOS 14.1, ElementalX 4.14, Magisk v14.0 and substratum with Flux (white) theme. I uninstalled XPosed but there are no significant differences, it's just about the same.
Anyone could give me a feedback? Thank you!
Skailog said:
Good day, I have a little problem with my 5x, when I long click on the power button, the power menu doesn't appear. Instead, I go to the boot animation and it just restarts, without showing the Google's logo.
Note that I use LineageOS 14.1, ElementalX 4.14, Magisk v14.0 and substratum with Flux (white) theme. I uninstalled XPosed but there are no significant differences, it's just about the same.
Anyone could give me a feedback? Thank you!
Click to expand...
Click to collapse
Uninstall the theme and see if it still reboots randomly.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Uninstall the theme and see if it still reboots randomly.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No, the device reboots still. But it is not random, actually it only happen when I press and hold the power button.
I will try to deactivate Magisk
Skailog said:
No, the device reboots still. But it is not random, actually it only happen when I press and hold the power button.
I will try to deactivate Magisk
Click to expand...
Click to collapse
Hmm. Reinstall the vendor image that matches the monthly security date that your rom is based on. If that doesn't help, you'll probably have to clean flash the rom.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hmm. Reinstall the vendor image that matches the monthly security date that your rom is based on. If that doesn't help, you'll probably have to clean flash the rom.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Okay, so I did a new clean install, but the problem is still here. Is it possible that this occurs after installing a new application? I have installed a few and the problem showed after that
Skailog said:
Okay, so I did a new clean install, but the problem is still here. Is it possible that this occurs after installing a new application? I have installed a few and the problem showed after that
Click to expand...
Click to collapse
Yes. You can install your apps one at a time until you see a culprit.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Yes. You can install your apps one at a time until you see a culprit.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Roger Roger, thanks for your help!
Magisk v14.0 cause a lot of bug try 13.3 is better
Sofiane omega said:
Magisk v14.0 cause a lot of bug try 13.3 is better
Click to expand...
Click to collapse
Yeah. I have tried with Magisk v13.3 (and so I uninstalled v14) but the same problem occurs.
I will try with a new nightly of LineageOS asap and report here if ever I find a solution.
Skailog said:
Yeah. I have tried with Magisk v13.3 (and so I uninstalled v14) but the same problem occurs.
I will try with a new nightly of LineageOS asap and report here if ever I find a solution.
Click to expand...
Click to collapse
try paranoid android 7.3.0 are more better than LOS 14.1
substratum OMS support,Magisk 13.3 and BlueBorne Patch
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.
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.