Recent content by cousinit99

That was my reflex, but it doesn't show up in the SU list as denied. 🤷‍♂️

Has anyone else run into an issue where Magisk SU permission requests fail? The prompt appears, you grant access, but Magisk doesn't get the message for some reason and the requesting app ultimately gets denied SU. The only workaround I've found is to change the Automatic Response to Grant in...

Decryption for OOS12 is working for me on 3.7.0_12.

@Nebrassy FBEv1 build appears to be unable to decrypt data for OOS11.

Thank you!

Don't know if this will help, but I recently ended up soft-bricked with that same error after upgrading to a newer version of TWRP. I believe it had something to do with the way TWRP interacts with the /data partition, although I'm not sure how exactly. Anyway, I was able to get the phone...

Use the red OEM USB cable. I was getting the same error, and switching to the red OEM USB cable fixed it.

If you're getting a param preload failed error, I can confirm that not using the cable that came with the device can cause this. I was using a USB 3.0 cable, and the cable that comes with the phone is USB 2.0. After switching to the red OEM cable, the download worked.

Man, fingers crossed they release something that's compatible with OOS 11 soon. I am not blowing away my data partition. Uggh!

I'm really wanting to like this ROM, but I'm experiencing a pretty significant issue where doze refuses to leave alone apps that I tell it not to "optimize" battery use for. When my alarm doesn't go off because doze killed my alarm app, well... yeah...... There's a couple other apps that...

The last update broke something. It keeps telling me to allow Notification Access, even though it's already allowed. I had to revert to 6.3.2. All of the newer versions have the same problem. Hopefully a fix is coming for this.

Do you know whether or not it's a known issue that Magisk Hide stops working on its own after a fairly short, but undetermined period of time? Or does someone need to provide logs for that as well? Short of a 10,000+ line logcat, I'm not sure how else to provide one. The Magisk log doesn't...

Also not using a Samsung device. Yes, Samsung Pay is still detecting Magisk somehow, even when all Samsung apps are hidden in Magisk Hide and after the old MagiskManager folder has been deleted and related executables renamed. Hopefully topjohnwu has a solution.

Go into Magisk Manager settings, un-tick Magisk Hide, wait a couple seconds, and then re-tick it. For me, Magisk Hide currently has an issue where it stops working after a fairly short, but undetermined period of time. The cause is also undetermined at this point. Just disable and re-enable...

I don't have an answer for you, unfortunately; hopefully someone with more knowledge in this area will chime in. What I can tell you is that the reason you're crashing appears to be the same reason that I and others are crashing. Your log file tells the same story as the other guy a few pages...