apps keep on disappearing after a restart in rooted S8+ (SM955FD) - Samsung Galaxy S8+ Questions & Answers

hi, newbie here...
i bought this S8+ (SM-955FD) for my son, flashed latest TWRP, flashed latest stable Jesse's Kernel (Exynos) and rooted usning TWRP the latest Magisk.
am trying to install a monitoring app in this device (mainly to monitor my son) :angel: .
the problem is when ever I give a simple restart (reboot); this app disappears from device !!!!! like its being removed automatically.
what i have done is installed 3C toolbox and granted Root permissions and removed the following:
- device maintenance.
-device security.
-All KNOX.
further more; disabled Google play protect. device is working just fine with better battery life.
now every time a install the app and check that it's working and functioning fine. after a simple restart the app disappears or i can say deleted automatically.
what can delete the app (considering that its a malware)!! even though all security features are removed???!?!?
thanks in advance

Related

[Q]Galaxy Tab 10.1 problem

I purchased my tab in China. Samsung China has deleted all Google apps from the pre-installed rom. As a result, the Chinese GT 10.1 community has compiled an Google app pack (GoogleServeice_P7510.zip) to bring back those apps.
I flashed it immediately after I rooted the tab. The Google apps were installed successfully. I entered my google account after the boot and every google app was running without a glitch. But not long after that I found I could no longer enter browser settings anymore. It would always give me a FC when I tried to do so. I then downloaded the dolphin browser. So this problem was bypassed.
Then I found there was something wrong with the superuser, I could not adb remount/push, and it couldn't be revoked by the apps that required root access.
This problem was partially resolved later by flashing the OC kernel for GT 10.1, which secured adb privileges. But the superuser was still problematic. Then I found out that after I flashed any zip other than root.zip in recovery, be it the kernel.zip, the su_busybox_tools.zip or google_servicepack.zip, the superuser icon in the app drawer would always become 4 times smaller (2 time in both height and length) than the superuser app "installed" by root.zip, as well all other apps.
There seemed to be something wrong with this version of superuser app (small icon). Whenever I opened an app that required root access, the superuser prompt window would not pop out. But if I flashed the root.zip again, the big-icon superuser app would be back. And other apps can revoke it most of time. However, it was not perfectly stable. Somethimes, it still failed to be revoked. I have flashed the root.zip among the other 3 zips for many times to get this conclusion.
I then applied the V6 SuperCharger script and flashed the su_busybox tools for GT 10.1 right before that, because SuperCharger script required busybox. However, due to the superuser problem, the SuperCharger script was not fully working. After reboot, part of the settings was changed back to default, because 99supercharger.sh couldn't be run on boot with root and there's not init.d folder in GT Tab 10.1. Then I flashed the OC kernel hoping it will fix all the problems. After that, I surprisingly found out that I was able adb remount and push. But the icon of the superuser app was again back to the small one. So the apps requiring root could not revoke it for permission.
As a result, I flashed the root.zip again. At this moment, superuser works normally, even after some reboots. SetCPU and script manager are able to automatically acquired root access on boot. But when I rechecked the supercharger script, current pages(minfree) were still showing blank.
Other problems include backspace and enter keys not working in terminal emulator/console. And the problem I just found - the notification ringtone list in the system settings and other app (e.g. Gmail) settings was blank. I could not change ringtone, although the system can play it without problem. And the ogg files are still there in /system/media/notifications.
Since all Android devices works more or less the same. I hope some of you phone experts can shed some light on these problem. The user base of Android tabs has made it less supported than Android phones. It'll be highly appreciated if all these annoying problems get fixed.
Thank you!

Pokemon Go W/ Slimkat.

Newest update has blocked access to rooted phones. Even after hiding/ removing root access privileges (I've tried both hiding and un-rooting) I cannot log in, so I'm left only to assume that the version of the OS itself is blocked.
Simple question: Does anyone know of a way around this? I see hundreds of posts about magisk, but I cannot do that while using slimkat ( magisk requires android 5.0+)
I've really gotten into this game over the last coiuple months, but I refuse to revert to some vanilla stock version of android to play. If anyone could provide any info I'd greatly appreciate it.
I'd do what I always do when I need/want to run something of that nature: I install a "sacrificial ROM" alongside my Slim using MultiRom and boot into it when needed.
So...an app demands a non-rooted ROM? No problem: Here's a plain vanilla AOS sandbox for you to play in.
I'm playing to PoGo with any issues with SlimRom 6, I just deleted a file called su.bin from /system/bin and /system/xbin.
This erases root of the rom, and make it playable. Use SafetyNetHelper on Google Play Store to check if you pass the test (PoGo uses this test).
You can delete them (you have to delete both) on the file manager of TWRP.
The way i got mine to work(i can also use the Fake GPS hack with my POgo as well! ) is 1st i downloaded an already rooted(with SuperSU) rom for my phone off of xda and i installed the fake gps app through ucky patcher to make it a system app. i then downloaded a stock rom for my phone from here at xda, and i flashed it using Odin, this replaced everything to make it stock again but kept my system files(the fake gps app) so then all i had to do was redownload PoGo and login as normal and voila! their security check diverted and still able to fake gps it lol

[Magisk Hide] Device Certified, but Netflix isn't showing up.

Hey guys, I ask here for help because i'm unable to find a solution to this problem.
Here some information to my device:
OnePlus One
ROM lineage-14.1-20170807-UNOFFICIAL-Sultan-bacon
Root with Magisk v13.3
Magisk Hide is enabled
SafetyNet passed
Playstore shows Certified
No other modules.
Already tried
clearing PlayStore app data and reboot
DRM info from PlayStore, It's says supported.
Super Mario Run and other Apps that blocked for rootet devices appeared after i enabled Magisk Hide and passed SafetyNet, but i still cannot download Netflix.
I hope some of you have the same Problem or a solution for this.
I also dont see netflix on playstore. I live in VIetnam
I'm also experiencing this, tried with a couple of roms and it's the same on all of them. I think that maybe it's related to our opo that isn't completely eligible for nougat (no stock rom for it also) and google is blocking every opo+nougat regardless of actual safetynet status. It's only my thought though and waiting for a response from someone who knows for sure.
Have you tried PA yet? When I was on that ROM, I can install many apps which not available on Los and other ROM
I was on stock cos13 with magisk and it also didn't show up but it didn't really matter as I just downloaded the apk file
I thinks is on the kernel side that it detect the root , but try to download from apkmirror.com it should work fine
Updated everything to current versions. Still the same problem.
Is there any way to view the exact reasons why my device is not compatible?
This would be very bad.
On my girlfriends phone (Moto G3) everything is working fine. Same gapps and rom setup.
I finally got it working.
My current setup is:
- OnePlus One
- lineage-15.1-20180827-nightly-bacon
- Magisk-v17.0
| - Magisk Hide Enabled
| - Systemless Host Enabled
| - Hide Magisk Manager
- Magisk Module "Google Play Service Fix for Lenovo Vibe K5"
- open_gapps-arm-8.1-micro-20180901
It seems that it is necessary to falsify the device information, as Lisko has already mentioned, the OnePlus One is blocked by the Playstore for Netflix if the Android API is higher than the last official ota.
This is done by the Magisk module mentioned above.

Any ROM on which VR-Secure GO banking app works?

Hello,
In order to do online banking I need to receive the TAN.
But this app won't let me even start, it opens the browser and tells me it detected root,
so I disabled root in the settings, restarted, even cleaned the cache and reinstalled but it still won't let me use it.
Do you know any ROM that supports my banking app?
Or another question: Does it even matter which TAN app I use?
I'm all new to online banking.
Maybe you can check if it works on your ROM, please let me know.
Thanks for your time in advance!
You can use the banking app with magisk. you need the "airfrozen" app and freeze the magisk app before you use the vr banking app and it will work.
This doesn't work here.
Hiding Magisk with "Airfrozen" on a rooted S8 with stock rom let VRSecureGO-App still complain of the device being jailbraked or rooted.
I froze Magisk
root checker app says device is not properly rooted
deleted all Date of VRSecureGo in Settings/Apps
VRSecure not working as described
On a Lineage 16 on installed on a S5 mini without root VRSecureGo won't work either.

MicroG Bricked Whole Phone

Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
bitblocksplicer said:
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
Click to expand...
Click to collapse
Which ROM are you actually running?

Categories

Resources