Hello everyone. I've always used the device with root access and it works very well, but I noticed that some things didn't open anymore, like EA Games games (Fifa, Madden, Sims. When they open and the screen rotates, it locks automatically, and keeps rotating the screen blocked until it locks), and some banking apps open and close. As I use Magisk, I put all of them to hide, but the problem with these specifics continues. I use Android 10 in its last update, I formatted the device, and the problem continued. I downgraded to Android 9 and returned to normal operation, but when I did the root, it started all over again. Has anyone seen this problem and would know how to guide me how to solve it? What else would I need to hide in the Magisk Manager (I put all the system files and also did not solve). Appreciate!
I'm on evolution and I did everything I could (in magisk) but still facing same problem.. I think there is no solution.. only solution is to flash back stock ROM and not rooting it.
Related
Hello, mates!!
I have a little problem with Dark Knight game in my unrooted Galaxy Note 8 (4.2.2)
About months ago i had version 1.1.3 installed and worked just fine, but i had to delete it because i needed internal storage space.
This week i tried to install it again, but when i start new game and tryin to play intro video, the game freezes (black screen with only skip icon showing but inactive).
Had someone the same problem? Is there a fix?
I have tried almost every version but the same things happens.
So it's probably the android version or some settings fault since i used to play this game...
thanvot said:
Hello, mates!!
I have a little problem with Dark Knight game in my unrooted Galaxy Note 8 (4.2.2)
About months ago i had version 1.1.3 installed and worked just fine, but i had to delete it because i needed internal storage space.
This week i tried to install it again, but when i start new game and tryin to play intro video, the game freezes (black screen with only skip icon showing but inactive).
Had someone the same problem? Is there a fix?
I have tried almost every version but the same things happens.
So it's probably the android version or some settings fault since i used to play this game...
Click to expand...
Click to collapse
Run saferoot and root your device. You can get it on the Easy way to root.. thread.
Once you root, download Ti backup and have it uninstall orphan apps. Somewhere in the system there are files that are left over from your game.
Safe root will not flash increment your counter so performing stock update will function normally. The only issue is Samsung Book Hub will not run in rooted devices. You can hide the root using substrate and Rootcloak to allow apps that do detect rooting to function.
If you are not willing to saferoot... then backup your apps and settings with Kies, and do a factory reset of your system. Then restore your apps and settings before installing your game.
If the game still does not run properly after any of the options I gave, then it is possible you are side-loading part of the app. Some apps like Samsung's Link will not side load properly without permissions and data properly transferred.
Since your not rooted at this time, doing any manual work to fix the issue will not be an option..
gooberdude said:
Run saferoot and root your device. You can get it on the Easy way to root.. thread.
Once you root, download Ti backup and have it uninstall orphan apps. Somewhere in the system there are files that are left over from your game.
Safe root will not flash increment your counter so performing stock update will function normally. The only issue is Samsung Book Hub will not run in rooted devices. You can hide the root using substrate and Rootcloak to allow apps that do detect rooting to function.
If you are not willing to saferoot... then backup your apps and settings with Kies, and do a factory reset of your system. Then restore your apps and settings before installing your game.
If the game still does not run properly after any of the options I gave, then it is possible you are side-loading part of the app. Some apps like Samsung's Link will not side load properly without permissions and data properly transferred.
Since your not rooted at this time, doing any manual work to fix the issue will not be an option..
Click to expand...
Click to collapse
Wow, thanks for your advice... I don't feel like rooting this baby for a while.. but i will try factory reset when i find time to.
I'm not sure i understood what side-loading is... but i'm 100% sure that somewhere in the system there are files that are left over. I wish i could find them or perhaps a Kitkat update sometime soon maybe help. Anyway, i'm going to try new games and then come back with this...
So, i've used Snapchat on both
Stock (5.1.1 - Oi1 Rom) and Custom Rom (Renegade)
I can't seem to get it to work on the custom rom, i've always had to use the stock rom and it would work just fine, but on the other it would say "temporarily logged out" or something different, but when i boot back to stock, its fine and doesn't hesitate to say that.
Am i missing something here?? i've already tried resetting my password 5 times to be sure.
Snapchat 9.1.17.1.0 -- Xposed Snapprefs 1.6.2
Snapchat and Root
I don't use Snapchat, but this might explain your issue:
http://www.xda-developers.com/snapchat-is-at-it-again-and-blocks-root-users-but-for-how-long/
Snapchat detects Root and stops working, XDA builds a work-around into Xposed, Snapchat puts out a new patch and repeat.
Found something new: Try updating to Snapprefs 1.6.4. And you will find more help here: http://forum.xda-developers.com/xposed/modules/app-snapprefs-ultimate-snapchat-utility-t2947254
Thank you!
I've actually ended up researching and figuring it outmyself my way or work around.
Snapchat checks or scans to see if "Xposed" which leads me to not log in.
So in order to use Snapchat with Snapprefs or 3rd party, you would need to either
Install stock and root it, then log into snapchat with the latest version and then go to recovery to install xposed.
or
Install stock and root then boot to recovery to install the custom rom and do no install xposed framework.
Once done with booting up and setting up, install snapchat latest version, log into it and then install xposed.
once thats done download 'xinstaller' and check to enable downgrading and updating and then install 'snapprefs' for all the
juicyness of customizations.
Profit!
My configuration.
Snapchat -
9.17.1.0
Xposed -
75 wanam 20151008 - seems to work best for me on both roms instead of v79.
Snapprefs -
1.6.2
koop1955 said:
I don't use Snapchat, but this might explain your issue:
http://www.xda-developers.com/snapchat-is-at-it-again-and-blocks-root-users-but-for-how-long/
Snapchat detects Root and stops working, XDA builds a work-around into Xposed, Snapchat puts out a new patch and repeat.
Found something new: Try updating to Snapprefs 1.6.4. And you will find more help here: http://forum.xda-developers.com/xposed/modules/app-snapprefs-ultimate-snapchat-utility-t2947254
Click to expand...
Click to collapse
I found a work around for it my phone died and I signed into my sc from another device used it and logged off when I tried signing in on my phone I got temp login failure notice this is what I did to get back on:
On a second device, download latest version and sign into Snapchat
Once done, root second device and download titanium backup
Make a back up of Snapchat from second device and send the .tibkp back up or whatever to the first device
On first device download latest version of snapchat and titanium back up and restore the data only from the file you sent to the first device from the second device
Once done use sc like normal
Works fine unless you sign out from Snapchat on the second device so what I did is I froze Snapchat on the second device and erased the back up.
Why does Snapchat do this? Does anyone have any idea why?
MafiaIlluminati said:
Why does Snapchat do this? Does anyone have any idea why?
Click to expand...
Click to collapse
They make a silly app with an unenforceable premise, the app sucks and they block third-party alternatives, their security is awful, their background data drain is known to go nuts, and now they are blocking root users so they can better charge you for replays??
But still they can't tame the root..
p.s. the CEO is an Apple fanboy..
I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.
Looks like Magisk 14.5 might have something to do with it.
Starting on page 452 there are a few posts from there on about it.
Symptoms are a random reboot with a soft boot loop of the SystemUI. The only way to correct it is to hard reboot the device.
I can usually go a few days worth of up time between the bug reappearing.
I was the exact same way on 8.0. Every couple of days, it would start randomly rebooting and/or apps would start crashing. The only fix was to hold the power button until it rebooted. Rebooting by just pressing the power button and selecting reboot would always hang.
I was hoping 8.1 would fix it, but it's quite a bit worse. It's done it at least 4 times so far today. Same symptoms. Apps will start crashing (sometimes the foreground app, sometimes background ones), or the phone will just soft reboot, or both. Sometimes it's while I'm using it, sometimes I'm not using it at the time. No rhyme or reason, that I can tell..
I had one app that crashed immediately every time I tried to start it until I uninstalled it and restored it from backup (with data). That was weird.
If this keeps up, I may have to roll back to 8.0.
theycallmerayj said:
I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.
Click to expand...
Click to collapse
There is a larger thread on this HERE. There is no definitive smoking gun yet but certain root apps seem to be causing it. One way to rule out Magisk would be to simply uninstall the app temporarily (longpress>>App Info>>Uninstall) then fastboot flash the original boot.img and dtbo.img. Run this way long enough to know for sure whether being rooted is causing the issue. There are tons of people rooted who do NOT have this issue, so it is more than likely one of your root apps/themes is causing it.
Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.
theycallmerayj said:
Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.
Click to expand...
Click to collapse
Have you tried Adaway? I use very few root apps, but that is the first one I add every time. I've not had any reboots at all and it is very effective. Because you only use the one root app, you may find the culprit was UH, and not Magisk.
I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots
theycallmerayj said:
I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots
Click to expand...
Click to collapse
You can use different host files you don't have to use the ones that come with AdAway. Try Steven blacks out
I'm having this same issue with Magisk. I experienced it with an older Magisk on 8.0 as well.
I'm thinking about just getting rid of Magisk altogether. However, I used ES File Explorer to edit my build.prop to add the command to disable the nav bar. I'm nervous that uninstalling Magisk will cause the "your system is corrupt" message and a bootloop. However, I also have Flash Kernel installed. I wonder if the custom kernel will allow me to use the phone with the modified build.prop and without Magisk...
Hey Good Morning folks.. I bought a new phone J6+ and I didn't care for warranty and I decided to void it and root my device. I updated my phone to the latest software from Samsung through Odin and everything went well. I downloaded Magisk Manager after that then pulled the boot image from the stock room I have using 7-zip and patched it then flashed it to my phone through Odin. As in such case it was supposed to work as it worked with all other Samsung devices I rooted.
After that I downloaded Solid Explorer and I tried to remove some apps from my /system/apps as a simple test to see if my root works. it was Youtube it wasn't a dangerous critical app. But then my phone hanged and restarted then I found Youtube is back.
I went to Magisk again and downloaded BusyBox from there and installed an app called "Uninstall System Apps" and I used it to remove Youtube also as a test it removed it and the restarted the phone flawlessly then I went to remove "Facebook" then restarted my phone then Gosh Youtube is back and also Facebook.
I found out if I try to modify anything in /system the phone will restart then undo what I've done.
what is the reason? is it Defex? is it RMM? is it Knox? is it DM-VERITY? I just wanna know what is wrong with it to see how I can fix it.
Edit:
Phone: SM-J610F/DS
Software Build: M1AJQ.J610FXXU1ASA3
Magisk version: 18.1
I keep reading other threads and posts. I can see there is a way using Ashyx Method https://forum.xda-developers.com/ga...ecovery-twrp-3-2-3-1-galaxy-j6-j610f-t3875150
I just wanna know why it fails if I install Magisk with "Patched Boot method" only.
Hi,
How can I fix the Play Protect certification in Google Play without using Magisk? I already tried the method of registration the Device ID Framework (Google Service Framework (GSF)) in the Google’s Device Registration page (https://www.google.com/android/uncertified) but the status still not verifiend.
Should I lock the bootloader? If yes, can I have problem doing that with a Custom ROM and when I brick the phone again (needing flashing the Fastboot ROM)?
About that...this is a Custom ROM problem or what? I don't want use Magisk because I got some apps problem even using Magisk Hide and I realy don't need use a root device. So I solve the problems with the apps taking off the Magisk, but I got a new problem with Play Protect that don't let me install some apps like Netflix from Play Store. This is a problem that I don't want have.
I was using my Mi9SE (grus) with original ROM for 2 years and this week I chose put a Custom ROM, so I did it with Xiaomi.eu (xiaomi.eu_multi_MI9SE_V12.0.3.0.QFBCNXM_v12-10). I've bricked and learn a lot of things with this choice, but there's some that I didn't find solutions. Since I'm "old school", I need to know if I will have more awnsers from Telegram than here?
Tks!
I found this "solution":
1) Through TWRP clear the folder /data/data/com.google.android.gms/app_dg_cache
2) Set the permissions (chmod) 0644 the folder /data/data/com.google.android.gms/app_dg_cache
May need to clear GPay data after reboot
GPay works on my POCO F2 Pro, no Magisk, no Google Play certification
from here (https://xiaomi.eu/community/threads/miui-12-0-stable-release.56191/page-124#post-574285)
The Play Protect still not passing (shows up not verified) BUT you can install the apps like Netflix normally.
So...it's working without ROOT, MAGISK and with UNLOCK bootloader.
EDIT: with that "solution" I started witnessing some bugs from Contacts in WhatsApp and higher time to install apps from Google Play.